New report2026 State of AI at Enterprise RIAs2026 State of AI at RIAsRead it freeOn demandOther eventsNext: AI for Mid-Sized Law, Nov 5
Ironclad APIIntegration guide

Integrate the Ironclad API.Caddi writes and runs the integration for you.

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.

  • 99%of agent runs complete successfully
  • ~45 minon average to build your first agent
  • 1M+back-office tasks completed
01Getting access

The connection is a project before it does anything.

Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. 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.

On your own

Register an app, store Ironclad credentials, refresh tokens and code around the rate limits.

With Caddi

Connect your Ironclad account once. Caddi holds the connection.

02The whole job

The job doesn't stop at Ironclad.

An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Ironclad API only reaches Ironclad.

On your own

Each extra system is another API, another set of credentials, another integration to own.

With Caddi

One automation runs across every tool the job touches, each through its API.

03After launch

Someone has to own the code.

API versions change, fields get added and your process moves.

On your own

A developer patches and redeploys the integration each time.

With Caddi

The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.

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.

When to build the Ironclad integration in-house

When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Ironclad work off someone's desk, the build is the slow part, and Caddi does it for you.

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.

Everything Caddi does with Ironclad.

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. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.

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.