Ironcladapp Ironclad Public API

Name: Ironclad Public API
Brand: Ironclad Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey41 Endpoints

Install Jentic One Beta

Connect the Ironclad Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ironclad Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fironcladapp.com%2Fironclad-public-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fironcladapp.com%2Fironclad-public-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Ironclad Public API.

Create contract workflows synchronously or asynchronously and track the resulting job

List, retrieve, and update workflow approvals across reviewers and roles

Manage signature requests, signers, and signing status on workflows

GET STARTED

Start building with Ironclad Public API

Explore with Jentic One

View OpenAPI Document

For Agents

Create and manage contract workflows in Ironclad - kick off a workflow, track approvals and signatures, list participants, and react to lifecycle events via webhooks. Useful for legal-ops automation and contract intake pipelines.

Use for: Launch a new contract workflow in Ironclad for an NDA, Check the status of an asynchronous workflow creation job, List all approvals on a specific workflow, Update the approver role for a contract review

Not supported: Does not handle e-signature legal evidence, document storage, or AI redlining - use for Ironclad workflow, approval, and signature orchestration only.

Use Cases

Patterns agents use Ironclad Public API for, with concrete tasks.

★ Self-Service Contract Intake from a Form

Sales or procurement teams expose a Typeform, Slack form, or internal portal that creates a contract in Ironclad as soon as a request is submitted. POST /workflows kicks off a synchronous workflow with the captured fields, while POST /workflows/async handles long-running templates without blocking the form. Integration takes a couple of days end-to-end.

POST /workflows with the captured form fields, then poll GET /workflows/{id} until the workflow reaches the review step.

Approvals and Signature Tracking in CRM

Revenue ops teams pull approval and signature state for each open Ironclad workflow back into their CRM so the deal owner sees blockers without leaving the opportunity record. GET /workflows/{id}/approvals and /signatures provide the per-role state, and webhook subscriptions push updates as they happen.

Fetch GET /workflows/{id}/approvals and /workflows/{id}/signatures for each open workflow and update the matching opportunity record with the next pending step.

Redline-Driven Workflow Revert

When a counterparty returns redlines after the review step, legal ops can revert the workflow programmatically rather than asking the owner to click through the UI. PATCH /workflows/{id}/revert-to-review moves the workflow back, then the team re-routes the updated draft for approval. Reduces manual handling on every redline cycle.

Call PATCH /workflows/{id}/revert-to-review on workflows where the counterparty returned redlines and notify the owner to re-launch approvals.

Lifecycle Webhooks into a Data Warehouse

Legal data teams subscribe to contract lifecycle webhooks so that workflow launches, approvals, and signatures land in their warehouse in near real time. Combined with periodic GET /workflows snapshots, this supports cycle-time analysis and bottleneck reporting across templates and counterparties.

Subscribe to workflow webhooks via the webhooks endpoints and write each event into the warehouse with workflow ID and event type.

Agent Contract Operations via Jentic

An AI assistant supporting legal ops can answer 'where is the Acme MSA right now?' or kick off a renewal workflow through Jentic. The agent searches by intent, Jentic returns the matching Ironclad operation with its API-key-protected schema, and the Authorization header is injected from the vault.

Use Jentic to search for 'create an Ironclad workflow', load the POST /workflows operation, and execute it with the workflow template and form fields supplied by the user.

Key Endpoints

41 endpoints — ironclad's public api gives programmatic control of contract workflows, records, approvals, signatures, and webhooks inside an ironclad workspace.

METHOD

PATH

DESCRIPTION

POST

/workflows

Create a workflow synchronously

GET

/workflows

List all workflows

POST

/workflows/async

Create a workflow asynchronously

GET

/workflows/async/{asyncJobId}

Retrieve the status of an async workflow create job

GET

/workflows/{id}

Retrieve a specific workflow

GET

/workflows/{id}/approvals

List all approvals on a workflow

GET

/workflows/{id}/signatures

List all signers on a workflow

PATCH

/workflows/{id}/revert-to-review

Revert a workflow to the review step

POST

/workflows

Create a workflow synchronously

GET

/workflows

List all workflows

POST

/workflows/async

Create a workflow asynchronously

GET

/workflows/async/{asyncJobId}

Retrieve the status of an async workflow create job

GET

/workflows/{id}

Retrieve a specific workflow

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Ironclad Public API by hand means generating a bearer key, sending it in the Authorization header, and picking the right regional host among the US, EU, demo, and preview servers for every workflow call. Through Jentic you install once, import the Ironclad Public API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Ironclad puts the workflow id in the URL path (/workflows/{id}/...), so a rule can pin your agent to one workflow: it can read that workflow's approvals and signatures and nothing else. You choose the operations it may call, so state changes like revert-to-review are not included unless you add them.

Credential isolation

Your Ironclad API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'launch a contract workflow', and Jentic returns the matching Ironclad operation with its input schema, so the agent fills in the workflow fields without reading the reference docs.

FAQs

Specific to using Ironclad Public API through Jentic.

What authentication does the Ironclad Public API use?

Ironclad uses an API key passed in the Authorization header on every request. Through Jentic, the API key is stored in the encrypted vault and injected at execution time, so the agent never handles the raw value.

Can I create contract workflows asynchronously?

Yes. POST /workflows/async creates a workflow asynchronously and returns an asyncJobId, which you poll via GET /workflows/async/{asyncJobId} until completion. Use this for templates that take longer to render.

How do I track approvals and signatures on a workflow?

GET /workflows/{id}/approvals lists role-by-role approval state, GET /workflows/{id}/approval-requests returns outstanding requests, and GET /workflows/{id}/signatures lists signers and signature status.

Can I revert a workflow back to the review step?

Yes. PATCH /workflows/{id}/revert-to-review moves a workflow that has progressed past review back to the review step, which is useful when counterparties return redlines.

What are the rate limits for the Ironclad Public API?

Ironclad does not enforce strict per-minute caps in the spec; throughput is governed by your workspace plan. Bulk operations should be paginated and respect the standard HTTP retry headers when present.

How do I create a workflow through Jentic?

Search Jentic for 'create an Ironclad workflow', load the POST /workflows operation, and execute it with the workflow template and form fields. Jentic injects the Authorization header from the vault.

Can I limit what my agent is allowed to do with the Ironclad Public API?

Yes. Because you run Jentic One yourself, your own rules decide which Ironclad operations and credentials the agent may use. Since Ironclad puts the workflow id in the URL path (/workflows/{id}/...), a rule can pin the agent to a single workflow so it reads only that workflow's approvals and signatures. You pick the operations it can call, so state-changing actions like PATCH /workflows/{id}/revert-to-review are excluded unless you add them.

Ironcladapp Ironclad Public API

Connect the Ironclad Public API to your agent

Capabilities

Start building with Ironclad Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs