After launching a workflow (synchronously or asynchronously), capture the workflowId from the launch response or job result
Retrieve the workflow record with GET /public/api/v1/workflows/{workflowId}; the response includes workflow status (e.g., in-progress, completed), the assigned approvers, the current step, and a link to the associated contract document
Access attached document metadata via the documents array in the workflow response; each entry includes a documentId, type, and a download URL valid for a limited time
List all record properties for the workflow using GET /public/api/v1/records/{recordId} (the workflowId and recordId are often the same in Ironclad); map the returned attributes to your CLM data model
Subscribe to workflow events via Ironclad's webhook configuration in the admin dashboard to receive real-time status changes rather than polling
Known gotchas
Document download URLs returned in the API response are time-limited pre-signed URLs; download and store files promptly rather than saving the URL for later use
The Ironclad API distinguishes between workflow objects and record objects; a completed workflow creates a record, but in-progress workflows may not yet have a fully formed record — check workflow status before querying the record endpoint
OAuth scopes are granular; read access to workflows (public.workflows.readWorkflows) and read access to records (public.records.readRecords) are separate scopes and both may be needed
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp