canonical: https://jentic.com/apis/ironcladapp.com

# Ironclad APIs

Ironclad is a contract lifecycle management platform. Its APIs let you create and manage contract workflows, track approvals and signatures, list participants, react to lifecycle events through webhooks, and authenticate integrations by exchanging an API key for a short-lived access token and discovering the resources an integration can act on.

## For AI agents

An agent can authenticate against Ironclad, obtain an access token, discover available resources, then create contract workflows, track approvals and signatures, revert workflows to review after redlines, and subscribe to lifecycle webhooks. This covers legal-ops automation from credential bootstrap through full contract intake and status tracking.

## Scope

Use for: Programmatic Ironclad contract workflow creation, approval and signature tracking, participant management, resource discovery, and lifecycle webhooks

Not supported:
- AI redlining
- document storage
- e-signature legal evidence
- sales quoting
- cycle-time dashboards

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Ironclad Public API | productivity | 41 | Create and manage contract workflows in Ironclad - kick off a workflow, track approvals and signatures, list participants, and react to lifecycle events via webhooks. |
| Ironclad API | productivity | 3 | Authenticate against Ironclad with an API key, exchange it for an access token, and list or retrieve generic resource records that catalogue what the integration can act on. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Authenticate and exchange an API key for an access token | ironcladapp | The Ironclad API spec exposes POST /auth/token and resource discovery to bootstrap an authenticated session. |
| Create and manage contract workflows, approvals, and signatures | ironclad | The Ironclad Public API spec carries the 41 workflow, approval, signature, participant, and webhook endpoints. |
| Validate which resource IDs are available before acting | ironcladapp | GET /resources and GET /resources/{id} let an integration confirm valid identifiers before launching workflows. |
| React to contract lifecycle events in near real time | ironclad | The Public API provides webhook subscriptions for launch, approval, and signature events. |

## Cross-API use cases

### Bootstrap then launch a contract workflow

An integration first exchanges its Ironclad API key for an access token and confirms the target resource exists, then creates a contract workflow with the captured intake fields. Using the auth spec to validate credentials and resources before the workflow call keeps failed launches out of the pipeline.

Example prompt: POST /auth/token on the ironcladapp spec, GET /resources to confirm the template, then POST /workflows on the ironclad spec with the intake fields.

### Monitored contract intake pipeline

Operations teams run a periodic healthcheck that exchanges the key for a token and lists resources, and when it passes the pipeline creates workflows and tracks approvals and signatures. This ties credential and access validation to the live contract operations so a broken integration is caught before contracts stall.

Example prompt: Run POST /auth/token and GET /resources on the ironcladapp spec as a healthcheck, then on success fetch GET /workflows/{id}/approvals and /signatures on the ironclad spec for each open workflow.

### Agent-driven contract status assistant

An assistant supporting legal ops obtains an access token, resolves the resource the user names, then answers where a contract stands and can revert a workflow to review when redlines arrive. Combining the discovery layer with the full workflow surface lets one agent go from credential to a specific contract action.

Example prompt: POST /auth/token and GET /resources/{id} on the ironcladapp spec to resolve the contract, then GET /workflows/{id}/approvals or PATCH /workflows/{id}/revert-to-review on the ironclad spec as the user requests.

## Why Jentic

- **Setup:** Wiring Ironclad by hand means generating an API key, running the token exchange, picking the right regional host, and sending headers on every workflow call across two specs. With Jentic you install Jentic One once, add the Ironclad APIs from the Jentic directory, store the key once, and your agent calls both specs.
- **Permission scoping:** Ironclad puts the workflow or resource id in the URL path, so your own rules in your Jentic One instance can pin an agent to one workflow or resource and to specific operations. State changes such as revert-to-review are excluded unless you add them.
- **Credential handling:** Your Ironclad API key is stored once, encrypted, by your own Jentic One instance and injected into the request header at execution time. It never enters the agent's prompt, logs, or context, and neither does the access token returned by the auth exchange.
- **Discovery method:** Agents search the Jentic directory by intent such as 'get an Ironclad access token' or 'launch a contract workflow', and Jentic returns the matching Ironclad operation with its input schema, so the agent fills in the fields without reading the reference docs.

## Related vendors

- **PandaDoc** — Document automation, e-signature, and CPQ for sales-led deals; an alternative when the focus is quoting rather than legal-ops review.
- **Juro** — Browser-native contract automation with templates and approvals; an alternative for lightweight in-browser editing.
- **Greenhouse** — Applicant tracking that hands off hire events to Ironclad for offer-letter and employment-contract workflows.

## FAQ

### What can I build across the Ironclad APIs?

You can bootstrap an authenticated session, discover the resources an integration can act on, and then create and manage contract workflows with role-based approvals, signature tracking, participant management, and lifecycle webhooks. Together the two specs cover legal-ops contract automation from credential exchange through full contract operations.

### Do I need both Ironclad specs?

Most production integrations use both. The Ironclad API spec handles authentication and resource discovery, and the Ironclad Public API spec carries the 41 workflow, approval, and signature endpoints. You can start with either, but real contract operations run against the Public API after the auth spec has provided a token.

### Does one credential cover both Ironclad specs?

Yes. Both specs authenticate with an Ironclad API key, so a single key works across them. The auth spec exchanges that key for a short-lived access token that downstream workflow calls can use.

### What kinds of contracts and teams does Ironclad suit?

Ironclad is built for legal-ops contract workflows such as NDAs, MSAs, and offer letters that need structured intake, role-based approvals, and signature tracking. It handles redline cycles through a revert-to-review step rather than sales-led quoting or lightweight in-browser editing.

### Can I track contract status and lifecycle events programmatically?

Yes. You can fetch per-role approval and signature state for any workflow and subscribe to webhooks for launch, approval, and signature events, so a CRM, warehouse, or assistant can reflect where a contract stands without anyone opening the Ironclad UI.

### How does Ironclad handle counterparty redlines?

When a counterparty returns redlines after the review step, you can move the workflow back with the revert-to-review operation instead of asking the owner to click through the interface, then re-route the updated draft for approval. This automates the handling on every redline cycle.