Ironclad's Public API Overview – Ironclad

This article will provide you with an overview of Ironclad's public API.

This article is geared towards a business audience. Technical documentation for Ironclad’s API is made available at https://developer.ironcladapp.com. Developers, please use that documentation.

To get started with Ironclad’s API, reach out to your Customer Success Manager to get API access enabled on your account.

If you are interested in Ironclad CLM API updates, refer to the Ironclad API Changelog. Want to be updated about the latest and greatest changes to Ironclad's APIs? In your favorite RSS reader, add this link to subscribe for updates.

What is Ironclad’s API?

Ironclad has an open application programming interface (API) that provides you with programmatic access to the data in your Workflow and Repository. Simply put, our API allows you to ask Ironclad for data about your contracts and receive it back in a structured format. The API is commonly used for bulk exporting data and integrating Ironclad with other third-party systems.

What is Ironclad’s API Main Functionality?

Ironclad’s API currently consists of three main sets of functionality: workflow endpoints, records endpoints, and webhooks. An endpoint is one end of a communication channel. For example, if you want to push a customer name from Ironclad to Hubspot, you must identify an endpoint on the Ironclad side to get the customer name from, and then an endpoint on the Hubspot side to receive the customer name.

Workflow Endpoints

Workflow endpoints provide data about in-progress, canceled, and completed workflows. For example, if you want to use a business intelligence tool, such as Periscope or Tableau, to visualize your in-progress contracts by status and agreement type, you can perform an hourly query on in-progress workflows to produce real-time analytics.

The following functionality will be live on July 10th. To learn more about the features included in our July release, refer to What's New in Ironclad: July 2025.

View a Workflow’s Field Details

You can also use workflow endpoints to view a workflow’s key field details, including:

Whether or not a field is required. There are three possible values:
1. Always: The field is referenced by a single, required, always visible question.
2. Never: All questions referencing the field are not required.
3. Conditionally: The field is referenced by 2+ questions and at least one is required, or visibility of the field is conditional.
All possible values for the field.
All default values for the field.

To learn more about retrieving these details, refer to Retrieve a Workflow Schema.

Records Endpoints

Record endpoints provide data about completed contracts that are stored in your Ironclad Repository. For example, if you want to create a new supplier record in your vendor management system, such as Oracle or Coupa, you can query the Repository nightly to make sure that you are creating an entry in your vendor management system for every completed supplier agreement.

Entity Endpoints

Entity endpoints allow you to sync entities in Ironclad with your preferred source of truth. For example, you might want to sync vendor data from your vendor management system to Ironclad entities.

Webhooks

Webhooks are a different from endpoints. Instead of being a tool to access information, they are a tool for Ironclad to say “Hey, I have new information for you!”. For example, if you want to post a celebratory message in Slack every time the sales team closes a deal, you can receive a webhook every time that workflow type is completed to trigger an instantaneous Slack message.

Get Started with Ironclad’s API

To get started with Ironclad’s API, reach out to your Customer Success Manager to get API access enabled on your account. Once you have API access, you can configure your API tokens and webhooks.

Warning: Treat your tokens like passwords and keep them secret. Never share a token via email, screenshot, etc. When you work with the API, use tokens as environment variables instead of hardcoding them into your programs. If you’re unsure on how to do that, talk to your company’s developer before generating a token.

Third-Party Tools

The following list contains helpful third-party tools our team recommends for API development:

Zapier: Build complex integrations using out-of-the-box integrations with hundreds of applications while writing minimal code. There is no need to set up infrastructure.
Postman: Rapidly test API queries and inspect responses.
Google Cloud Functions: Write simple, self-contained programs that can be triggered via webhooks. Enjoy the flexibility of your favorite programming tools, like Node.js or Python, without having to stand up a server.
Retool: Easily build internal company tools with clean user interfaces and sync data to and from other internal databases.