Ironclad APIConnect Ironclad without building on its API
Ironclad has a REST API. Customers only: API access must be enabled on the account by your Ironclad Customer Success Manager, and the /exports endpoint needs the paid Security and Data Pro add-on. If you're reading the docs because you need Ironclad to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Ironclad and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve for customers
What the Ironclad API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (authorization code or client credentials) bearer tokens
- Who can get access
- Customers only: API access must be enabled on the account by your Ironclad Customer Success Manager, and the /exports endpoint needs the paid Security and Data Pro add-on.
- What it covers
- Workflows (contract launches and approvals), records (executed contracts), entities, exports, and SCIM users/groups.
- Limits
- Per-bucket limits such as Workflows 400 read / 40 write RPM and Records 600 read / 200 write RPM, under a company-wide cap of 4,500 requests/minute.
Official docs: developer.ironcladapp.com. Checked September 2026. Vendors change access terms, so confirm with Ironclad before you build.
Building on the Ironclad API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Ironclad credentials, and manage tokens and refreshes. | Connect your Ironclad account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Ironclad task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Ironclad work off someone's desk, the build is the slow part.
What teams usually want the Ironclad API for
Email-to-workflow intake
Caddi reads inbound contract request emails, extracts the metadata, and kicks off the right Ironclad workflow with the file attached.
Signed-contract filing + CRM update
On signature, Caddi files the final contract to the right cloud storage folder and updates the matching record in Salesforce.
Obligation reminder loop
Caddi watches contract obligations and renewal dates, drafts the reminder, and routes it to the contract owner.
Ironclad API questions
Does Ironclad have an API?
Yes. Ironclad has a REST API, authenticated with OAuth 2.0 (authorization code or client credentials) bearer tokens. The official documentation is at https://developer.ironcladapp.com/.
How do I get access to the Ironclad API?
Customers only: API access must be enabled on the account by your Ironclad Customer Success Manager, and the /exports endpoint needs the paid Security and Data Pro add-on.
Does the Ironclad API have rate limits?
Per-bucket limits such as Workflows 400 read / 40 write RPM and Records 600 read / 200 write RPM, under a company-wide cap of 4,500 requests/minute.
Can I connect Ironclad to my other tools without writing code against its API?
Yes. With Caddi you show the Ironclad task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Ironclad and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Ironclad with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Ironclad is reviewed before it runs in production, and every run is logged.
Connect Ironclad without the build.
Drop your work email and pick a time. We'll show you Caddi running your Ironclad workflow end to end.