Generate an API key in Ironclad Settings and include it as the Authorization: Bearer token on all requests.
POST to /public/api/v1/workflows with a template key (the workflow schema ID from Ironclad), an attributes object containing form field values, and an optional signers array to initiate the workflow.
Poll GET /public/api/v1/workflows/{workflowId} to monitor the workflow's current step and status.
Use GET /public/api/v1/workflows to list and filter workflows by status, date range, or template; paginate using the nextToken cursor returned in each response.
Download executed contract documents via the download URL included in the workflow record's metadata once the workflow reaches a completed state.
Known gotchas
Attribute field keys must match the internal schema identifiers defined in the Ironclad workflow template, not their display labels — retrieve the schema definition first to map them correctly.
Ironclad's API rate limits are account-tier-dependent and not always documented publicly; contact Ironclad support to confirm limits before designing high-volume integrations.
Workflow progression may require human approvals that cannot be bypassed via API; design your polling logic to handle long-running or indefinitely-paused workflows.
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