Ironclad AI: API, Agents, Apps, and Workflow Automations
Understand Ironclad's native AI, OAuth scopes, API endpoints, webhooks, and rate limits. Build governed renewal queues and signature tracking on Major with persistent state and human approval.

Ironclad AI helps legal teams extract contract data, review language, and work with agreements inside Ironclad. This guide covers its built-in AI, verified API capabilities, and how to connect Ironclad to Major for governed work across systems.
On Major, agents build deterministic apps that hold contract state and review queues, while agents handle judgment and workflows coordinate execution. The practical audience is legal operations leaders connecting contract deadlines, signature progress, and business owners.
What Ironclad manages for legal operations
Ironclad is a contract lifecycle management system. Its developer guide distinguishes workflows from records: workflows represent the contracting process, while repository records hold completed agreements and their metadata.
That distinction determines where an integration reads. Legal operations monitors work moving through review and signature. Commercial counsel reviews negotiated language. Procurement tracks supplier agreements, and sales operations needs reliable execution status before treating a transaction as complete.
A renewal monitor generally starts with repository records. A signature exception queue starts with active workflows. Mixing those objects can produce misleading alerts, such as treating an unfinished agreement as an executed contract.
Keep the identifiers separate, too. A workflow design has a template ID, an individual negotiation has a workflow ID, and an archived agreement has a record ID. Ironclad also supplies a human-readable Ironclad ID across the lifecycle, as its getting-started guide explains.
Major adds the operational app around those objects: persistent links to business systems, owner assignments, notification receipts, and a review queue that survives individual conversations.
Ironclad AI: native capabilities and where Major fits
Ironclad already offers substantial AI functionality. Its AI overview describes Smart Import for extracting data from uploaded agreements, AI Clauses and Custom AI Properties for detection, and AI Playbooks for finding nonstandard terms and suggesting edits or additional approvals.
AI Assist helps draft redlines, edit language, and summarize committed text in Ironclad Editor. Contract Review Agent, formerly Jurist, supports drafting, editing, summarization, contract analysis, and legal research with citations. Its documentation labels precedent-based redlining and Playbook Agent as Early Access, so verify availability before designing around them.
These features belong close to the agreement and the legal review process. Major adds value when a decision needs context outside Ironclad: which supplier owner should act, whether a renewal conflicts with a business plan, or how to explain a signature delay to operations.
The agent makes that contextual assessment. Its app stores the evidence and decision history; the workflow obtains approval before consequential action. Do not assume every native AI feature has a public API simply because it appears in the product.
How Ironclad connects to Major
Ironclad has no native or Pipedream connector in the catalog: it connects as a custom API connector, with base URL and authentication configured once by IT. Major orchestrates Ironclad; it never replaces it.
For standard production, the API server is https://ironcladapp.com/public/api/v1. Confirm the tenant domain rather than copying it blindly. Ironclad documents separate production, EU, and demo environments, and OAuth clients are environment-specific.
IT registers an OAuth client, chooses permitted resource scopes, and stores credentials centrally in Major's connector vault, never in code or prompts. Ironclad's registration guide says the API settings tab requires the API add-on.
Start with read access for the contract types the operator needs. Separate the permission to read agreements from permission to update metadata or launch contracting processes. On Major, SSO, RBAC, and audit logs cover apps, agents, and workflows.
The initial build should expose a small set of approved operations, not unrestricted access to every endpoint. Keep legal content out of broad notification channels, and test the connector using the same user context intended for production.
Ironclad API guide for apps, agents, and workflows
Authentication and access boundaries
Ironclad primarily uses OAuth 2.0, supporting authorization code and client credentials grants. Requests use bearer authentication.
With the client credentials grant, requests must include either x-as-user-id or x-as-user-email. Effective access depends on both resource scopes and that user's permissions. Tokens expire after six hours, and this grant issues no refresh token; obtain another token through the grant.
The endpoint paths below are relative to the API server above, exactly as their reference pages show them. Their linked pages give the required scopes. For example, reading records requires public.records.readRecords, while metadata updates require public.records.updateRecords. Do not grant write scopes to a read-only renewal monitor.
Pagination, rate limits, events, and testing
Pagination uses page and pageSize, starting at page zero with 20 results by default. The maximum page size is 100. Persist progress between batches rather than restarting every scan.
Ironclad now publishes company-level rate limits. Workflow reads share 400 requests per minute; workflow writes share 40. Record reads allow 600 and record writes 200, with separate subresource buckets and a company-wide cap of 4,500 requests per minute.
Watch X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. On HTTP 429, Retry-After gives the wait in seconds. Leave headroom for other integrations using the same company quota.
Webhooks include workflow launches, step changes, completion, and contract status changes. Verify signatures using the event ID, JSON-stringified body, and nonce in the documented order, with the public verification key and algorithm from the verification specification. The relevant headers are X-Ironclad-Webhook-Event-Id and X-Ironclad-Webhook-Verification.
For most eligible errors, Ironclad retries up to ten times over 13.6 hours. It does not retry 400, 401, 405, or 422; HTTP 410 disables the webhook. Destination authentication also supports API key, basic, or bearer authentication over HTTPS.
A purchased sandbox instance may use a different base URL. A documented demo environment is not a promise of free sandbox access. Use approved test agreements and separate environment credentials.
GET /records: find the portfolio
Lists repository records with filtering options. Required scope: public.records.readRecords.
- App: Populate a contract inventory with source IDs and scan timestamps.
- Agent: Assess which approaching renewals deserve attention using returned metadata and approved business context.
- Workflow: Run a paginated daily scan and enqueue only eligible records.
GET /records/{id}: read one agreement's metadata
Retrieves a specific record and associated data. Required scope: public.records.readRecords.
- App: Show the current record alongside notification history.
- Agent: Draft a renewal brief that distinguishes missing information from verified terms.
- Workflow: Re-read the record before sending an alert so an outdated scan cannot drive action.
PATCH /records/{id}: apply a reviewed correction
Updates specified record fields. Required scope: public.records.updateRecords. Permission-grant fields have additional restrictions documented on the endpoint page.
- App: Present proposed old and new values in a review form.
- Agent: Suggest a correction when authorized sources disagree, with supporting evidence.
- Workflow: Wait for approval, apply the permitted fields, and verify the result.
GET /workflows: inspect active contracting
Lists workflows with status, template, and other query options. Required scope: public.workflows.readWorkflows.
- App: Maintain an execution queue separate from the repository inventory.
- Agent: Prioritize stalled agreements using deal context and owner notes.
- Workflow: Reconcile changed workflows against the last successful synchronization.
GET /workflows/{id}: refresh one negotiation
Retrieves an individual workflow's data. Required scope: public.workflows.readWorkflows.
- App: Display the current contracting stage and linked business record.
- Agent: Explain why a case needs legal attention instead of a routine reminder.
- Workflow: Fetch authoritative state after an event before routing the next task.
GET /workflows/{id}/sign-status: inspect signature progress
Returns sign-step information and requires the workflow to be in that step. Required scope: public.workflows.readSignStatus.
- App: Show signature progress beside the mapped DocuSign envelope reference.
- Agent: Draft an exception summary without assuming a missing signature means rejection.
- Workflow: Check the current stage first and stop sign-status polling after the workflow leaves it.
GET /workflow-schemas/{id}: validate intake
Returns fields used in a workflow launch form. Required scope: public.workflows.readSchemas.
- App: Render intake fields against the configured contract template.
- Agent: Identify ambiguous business inputs that need clarification.
- Workflow: Validate required inputs and refresh schema mappings when a design changes.
POST /workflows: launch approved work
Creates a workflow synchronously. Required scope: public.workflows.createWorkflows.
- App: Store the request, approval, and resulting Ironclad workflow ID.
- Agent: Propose the appropriate agreement process from the request context.
- Workflow: Launch only after authorization and reconcile uncertain responses before retrying creation.
GET /webhooks/verification-key: authenticate incoming events
Retrieves the public key used for webhook verification; follow the endpoint's authentication requirements.
- App: Store verification configuration and operational health, not private credentials.
- Agent: Summarize recurring intake failures from sanitized diagnostics.
- Workflow: Retrieve or refresh the key and reject unverified events before business processing.
Ironclad automation use cases on Major
Renewal alerts across Ironclad and Slack
- App: Track contract IDs, notice deadlines, owners, and 60/30/7-day notification receipts.
- Agent: Draft a risk summary from verified renewal terms and explain uncertainty.
- Workflow: Scan records, refresh each eligible agreement, and post an allowed internal reminder once per threshold.
Use GET /records and GET /records/{id}. Calculate alerts against the verified notice deadline, not automatically against expiration.
Signature visibility across Ironclad, DocuSign, and Slack
- App: Store workflow-to-envelope mappings and a separate exception queue.
- Agent: Explain delays and draft an internal escalation for the responsible owner.
- Workflow: Refresh workflow and sign-step state, reconcile it with the organization's approved DocuSign process, and route discrepancies for review.
Use GET /workflows/{id} and GET /workflows/{id}/sign-status. Tracking does not require creating a second envelope or bypassing Ironclad's signing process.
Contract intake from Salesforce into Ironclad
- App: Keep a request queue linking the business opportunity, approved inputs, and resulting contract workflow.
- Agent: Assess whether the request matches the selected agreement process or needs counsel's interpretation.
- Workflow: Validate the launch schema, obtain approval, and create the workflow once.
Use GET /workflow-schemas/{id} and POST /workflows. This is an illustrative extension, not a claim that every commercial field maps automatically to a legal field.
Architecture: build the contract operations layer on Major

Figure 1. Judgment sits in the agent; contract state and review history sit in the app.
Build one contract operations app with managed tables for source identifiers, current snapshots, recommendations, approvals, and delivery receipts. Give each process a visible status so an operator can distinguish waiting for review from waiting for a downstream system.
The trigger is either an authenticated event or a schedule. The workflow retrieves current data through scoped connectors, runs validation, and passes only relevant context to the agent. The agent assesses urgency or ambiguity and returns a recommendation with evidence.
Deterministic code handles date arithmetic, identifier mapping, duplicate detection, and queue transitions. Once the agent builds that repeatable software, subsequent runs use the app instead of asking the model to reconstruct the same procedure.
An approval gate checks whether the proposed action is permitted, requires a named reviewer, or must stop. The app holds that state through delays and retries. An output is complete only when its receipt is recorded, not merely when a model says it sent something. This is Major's reason once, run forever model applied to contract operations.
A worked example with renewal review numbers
For example, consider an illustrative legal operations team reviewing 200 upcoming renewals each month. Assume gathering metadata, checking ownership, and drafting an internal note currently takes 12 minutes per agreement: 200 × 12 = 2,400 minutes, or 40 hours.
The Major workflow scans records daily and stores the last successful scan. For each qualifying contract, it refreshes metadata and calculates the notice threshold in code. The agent drafts the business-facing risk explanation, citing the available source fields and marking unclear terms for review.
Suppose 160 straightforward cases then need three minutes of human review each, while 40 exceptions still require 12 minutes. Review time becomes 160 × 3 + 40 × 12 = 960 minutes, or 16 hours. The illustrative difference is 24 hours per month, before setup, maintenance, and quality sampling.
This estimates handling time, not avoided legal exposure or a customer result. Measure missing dates, incorrect owners, rejected drafts, and duplicate alerts alongside minutes saved. A faster queue is useful only if its deadline interpretation remains correct.
Governance, approvals, and failure handling

Figure 2. Internal reminders can follow policy; consequential changes wait for explicit approval.
Allow routine internal reminders only within approved templates, destinations, and data boundaries. The agent must never independently accept contract terms, waive rights, change signer authority, terminate an agreement, or send a counterparty notice. Record the reviewer, exact proposed action, input version, and approval time.
On retryable failures, preserve the task and back off. Honor the documented rate-limit headers, cap retries, and route exhausted work to an operator. After an uncertain create response, reconcile source and destination state before trying again.
Deduplicate events using the signed webhook event identifier, and fetch current state rather than assuming arrival order. Store notification thresholds separately so repeated scans do not resend the same alert.
Monitor webhook health: Ironclad documents automatic deactivation after at least 100 consecutive failures spanning at least six days without success. Reconciliation scans should detect gaps rather than treating webhook delivery as permanent proof of synchronization.
Ironclad AI Apps, Agents and Workflow Automations
These process guides focus on Ironclad as a core system, rather than mentioning it in a general tool list. They go deeper into the operating model for a particular legal operations queue without changing Ironclad's role as the contract system of record.
- Track Ironclad renewal deadlines and send reviewable Slack alerts: Covers the renewal countdown, agent-written risk summaries, and notification history. Read it when the immediate problem is knowing which owner must act before a notice window closes.
- Track Ironclad contract execution across DocuSign signatures: Covers persistent workflow-to-envelope links, signature visibility, and reviewable exceptions. Read it when legal operations loses context between approved agreement and completed execution.
Choose the process that already has an accountable owner and usable source data. Renewal monitoring needs verified notice terms; execution tracking needs reliable envelope mappings. For the broader operating model, see AI agents for legal and compliance, then scope one queue before expanding to additional contract types.
Frequently asked questions
What is Ironclad AI?
Ironclad AI is a set of capabilities for extracting contract data, reviewing language, and working with agreements inside Ironclad. Native features include Smart Import, AI Assist, AI Playbooks, and Contract Review Agent. Major adds governed cross-system apps and orchestration around that work.
Is Jurist still part of Ironclad?
Ironclad's documentation now calls Jurist Contract Review Agent. It supports legal drafting, editing, summarization, analysis, and research. Check current feature availability, especially capabilities labeled Early Access, rather than assuming older Jurist descriptions match your subscription.
Does Major have a native Ironclad connector?
No. Ironclad connects to Major through a custom API connector configured once by IT with the environment's base URL and authentication. Credentials stay in the connector vault, and apps, agents, and workflows use the scoped operations IT permits.
Can I automate contract renewal alerts without changing agreements?
Yes. A read-only design retrieves record metadata, calculates notice thresholds, and drafts internal summaries. The app stores owners and notification history. Require legal review when dates or terms are unclear, and keep external notices outside the automatic path.
What permissions does the Ironclad API need?
Permissions depend on the operation. Reading records requires public.records.readRecords; updating metadata requires public.records.updateRecords. Client credentials requests also need an acting-user header, and that user's permissions constrain access. Grant only the scopes the approved process uses.
Can an agent approve or sign contracts automatically?
Do not give a general contract operations agent that authority. Let it assess context and propose actions, while named people approve consequential decisions. Keep approval records in the app and enforce the boundary through workflow gates and connector permissions.
Sources
Official documentation used for the API behavior, environment requirements, and native AI descriptions in this guide:
- Getting started: workflows, records, and identifiers
- Authentication and environment base URLs
- Register an OAuth client and resource scopes
- Authorization code grant and user authorization
- Client credentials grant and acting-user permissions
- Authenticate a request with bearer tokens
- Pagination defaults and page size maximum
- Company quotas and rate-limit response headers
- Webhook event types and delivery retries
- Webhook signature verification procedure
- Webhook destination authentication options
- Webhook deactivation and monitoring requirements
- List records and available query parameters
- Retrieve a record and associated data
- Update specified record metadata fields
- List workflows and supported filters
- Retrieve an individual workflow's data
- Retrieve information for the sign step
- Retrieve a workflow launch form schema
- Create a workflow synchronously
- Retrieve the webhook verification key
- Ironclad AI features overview
- Introduction to Contract Review Agent, formerly Jurist
- AI Assist drafting, editing, and summarization
- Smart Import and AI Suggestions overview
Start building on Major
Build a contract renewal queue or signature exception app with persistent state, scoped Ironclad access, and human approval for consequential actions.
About the author
Ritvij Gautam is Head of Growth at Major.
Last reviewed November 20, 2026 by Ritvij Gautam.
Frequently asked questions
- What is Ironclad AI?
- Ironclad AI is a set of capabilities for extracting contract data, reviewing language, and working with agreements inside Ironclad. Native features include Smart Import, AI Assist, AI Playbooks, and Contract Review Agent. Major adds governed cross-system apps and orchestration around that work.
- Is Jurist still part of Ironclad?
- Ironclad's documentation now calls Jurist Contract Review Agent. It supports legal drafting, editing, summarization, analysis, and research. Check current feature availability, especially capabilities labeled Early Access, rather than assuming older Jurist descriptions match your subscription.
- Does Major have a native Ironclad connector?
- No. Ironclad connects to Major through a custom API connector configured once by IT with the environment's base URL and authentication. Credentials stay in the connector vault, and apps, agents, and workflows use the scoped operations IT permits.
- Can I automate contract renewal alerts without changing agreements?
- Yes. A read-only design retrieves record metadata, calculates notice thresholds, and drafts internal summaries. The app stores owners and notification history. Require legal review when dates or terms are unclear, and keep external notices outside the automatic path.
- What permissions does the Ironclad API need?
- Permissions depend on the operation. Reading records requires public.records.readRecords; updating metadata requires public.records.updateRecords. Client credentials requests also need an acting-user header, and that user's permissions constrain access. Grant only the scopes the approved process uses.
- Can an agent approve or sign contracts automatically?
- Do not give a general contract operations agent that authority. Let it assess context and propose actions, while named people approve consequential decisions. Keep approval records in the app and enforce the boundary through workflow gates and connector permissions.