Appearance
Ironclad
Manage contracts, workflows, approvals, and records via the Ironclad API.
| Detail | Value |
|---|---|
| Category | Legal |
| Base URL | https://ironcladapp.com/public/api/v1 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | ironclad |
Using Ironclad in a workflow
- Go to Connections and click New Connection.
- Pick Ironclad from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /workflows | List workflows |
POST /workflows | Launch a new workflow |
GET /workflows/{workflowId} | Get a workflow |
GET /records | List contract records |
GET /records/{recordId} | Get a contract record |
GET /templates | List workflow templates |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /workflows
List workflows
| Detail | Value |
|---|---|
| Operation ID | legal.listWorkflows |
| Method | GET |
| Path | /workflows |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
page | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ironclad connection from the Connection dropdown.
- In the Operation dropdown, select
legal.listWorkflows. - 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
| Detail | Value |
|---|---|
| Operation ID | legal.createWorkflow |
| Method | POST |
| Path | /workflows |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ironclad connection from the Connection dropdown.
- In the Operation dropdown, select
legal.createWorkflow. - 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
| Detail | Value |
|---|---|
| Operation ID | legal.getWorkflow |
| Method | GET |
| Path | /workflows/{workflowId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
workflowId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ironclad connection from the Connection dropdown.
- In the Operation dropdown, select
legal.getWorkflow. - 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
| Detail | Value |
|---|---|
| Operation ID | legal.listRecords |
| Method | GET |
| Path | /records |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ironclad connection from the Connection dropdown.
- In the Operation dropdown, select
legal.listRecords. - 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
| Detail | Value |
|---|---|
| Operation ID | legal.getRecord |
| Method | GET |
| Path | /records/{recordId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
recordId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ironclad connection from the Connection dropdown.
- In the Operation dropdown, select
legal.getRecord. - 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
| Detail | Value |
|---|---|
| Operation ID | legal.listTemplates |
| Method | GET |
| Path | /templates |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Ironclad connection from the Connection dropdown.
- In the Operation dropdown, select
legal.listTemplates. - 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.