Skip to content
For LLMsView as Markdown·

Ironclad ​

Manage contracts, workflows, approvals, and records via the Ironclad API.

DetailValue
CategoryLegal
Base URLhttps://ironcladapp.com/public/api/v1
AuthenticationBearer Token
Endpoints6
Connector keyironclad

Using Ironclad in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Ironclad from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET /workflowsList workflows
POST /workflowsLaunch a new workflow
GET /workflows/{workflowId}Get a workflow
GET /recordsList contract records
GET /records/{recordId}Get a contract record
GET /templatesList workflow templates

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /workflows ​

List workflows

DetailValue
Operation IDlegal.listWorkflows
MethodGET
Path/workflows

Parameters ​

NameLocationTypeRequired
pagequeryintegerNo

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Ironclad connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.listWorkflows.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Ironclad API reference.

POST /workflows ​

Launch a new workflow

DetailValue
Operation IDlegal.createWorkflow
MethodPOST
Path/workflows

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Ironclad connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.createWorkflow.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Ironclad API reference.

GET /workflows/{workflowId} ​

Get a workflow

DetailValue
Operation IDlegal.getWorkflow
MethodGET
Path/workflows/{workflowId}

Parameters ​

NameLocationTypeRequired
workflowIdpathstringYes

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Ironclad connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.getWorkflow.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Ironclad API reference.

GET /records ​

List contract records

DetailValue
Operation IDlegal.listRecords
MethodGET
Path/records

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Ironclad connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.listRecords.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Ironclad API reference.

GET /records/{recordId} ​

Get a contract record

DetailValue
Operation IDlegal.getRecord
MethodGET
Path/records/{recordId}

Parameters ​

NameLocationTypeRequired
recordIdpathstringYes

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Ironclad connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.getRecord.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Ironclad API reference.

GET /templates ​

List workflow templates

DetailValue
Operation IDlegal.listTemplates
MethodGET
Path/templates

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Ironclad connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.listTemplates.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Ironclad API reference.