← Back to all docs
ironclad

Ironclad API

Programmatically access contract workflows, templates, negotiations, approvals, signatures, and repository records from Ironclad with a stable REST API. Supergood builds and operates production-grade, unofficial Ironclad integrations so your team can automate CLM workflows without heavy custom engin

By Alex KlarfeldFebruary 20, 2026
Ironclad API

What is Ironclad?

Ironclad is a digital contracting platform that streamlines the entire contract lifecycle: intake, authoring, negotiation, approvals, signature, and post-execution management. It provides configurable workflows, collaborative review, native or third-party eSignature, and a searchable repository enriched with structured contract data.

Core product areas include:

  • Workflow Designer & Intake (self-serve contract requests, dynamic templates, conditional fields)
  • Authoring & Playbooks (clause library, fallback positions, MS Word add-ins, guided drafting)
  • Negotiation & Redlining (version control, comments, comparisons, internal/external collaboration)
  • Approvals & Collaboration (review routing, role-based stages, Slack/Teams notifications)
  • Signature Orchestration (Ironclad Sign and integrations with leading eSignature providers)
  • Repository & Search (metadata, clauses, renewal dates, obligations, full-text search)
  • AI & Smart Import (OCR, data extraction, automatic tagging, suggested fields)
  • Reporting & Audit (lifecycle metrics, throughput, immutable activity history)

Common data entities:

  • Contracts & Records (master record with lifecycle status and key fields)
  • Workflows & Templates (configurable processes tied to document templates and fields)
  • Documents & Versions (drafts, redlines, executed PDFs, comparisons)
  • Counterparties & Contacts (organizations, signers, stakeholder details)
  • Approvals & Tasks (stage assignments, outcomes, timestamps)
  • Signature Packets & Signers (signing order, method, completion state)
  • Fields & Clauses (structured metadata, clause variants, playbook rules)
  • Users, Groups & Permissions (requesters, approvers, legal ops)
  • Audit Events (who did what, when, with before/after values)

The Ironclad Integration Challenge

Turning a highly configurable, portal-first CLM into reliable, API-driven automation—especially when you also need to fit into an iManage-centric document workflow—introduces real complexity:

  • Dynamic templates and fields: Every workflow can have bespoke, conditional metadata that must be mapped and validated
  • Document versioning: Negotiations bounce between Word and the web; preserving versions and comments while syncing to iManage requires careful check-in/out handling
  • Approval routing: Parallel and sequential approvals span multiple teams and tools with SLAs and escalations
  • Signature orchestration: Multi-step eSignature packets and provider differences need asynchronous status management
  • Authentication & SSO: SAML/SSO and MFA complicate headless automation and require secure session lifecycles
  • Entitlements & visibility: Role- and group-based permissions must be enforced across requests and repository access
  • Long-running workflows: Reviews and signatures can take days; integrations need idempotent retries and job polling
  • DMS alignment: Matter numbers, workspace/folder conventions, and metadata mapping into iManage must remain consistent
  • Audit rigor: Every change must be traceable with immutable records and evidence

How Supergood Creates Ironclad APIs

Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your Ironclad tenant.

  • Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
  • Maintains session continuity with automated refresh and change detection
  • Normalizes workflow, contract, document, and signature objects so you can integrate once and rely on consistent schemas
  • Aligns with customer entitlements and role-based permissions to ensure compliant access
  • Supports high-volume operations with polling or webhooks for long-running steps (approvals, signatures, imports)
  • Offers optional iManage adaptors for workspace resolution, profile metadata mapping, and version check-in/out

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your modules, licensing, and authentication model.

  • Supergood Builds and Validates Your API

We deliver a hardened Ironclad adapter tailored to your workflows, fields, and iManage mapping.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Ironclad evolves.

Use Cases

Matter-Centric Contracting with iManage

- Auto-create or locate iManage workspaces from matter numbers captured in Ironclad intake - File drafts, redlines, and executed PDFs in the correct workspace/folder with consistent naming - Mirror Ironclad fields (e.g., counterparty, effective date, renewal) to iManage profile metadata

Negotiation & Redline Synchronization

- Push new versions from your editor or external counsel into Ironclad with automated check-in to iManage - Pull comparisons and comments to power review dashboards or knowledge capture

Approvals, SLAs, and Collaboration

- Publish approval tasks into Slack or Teams, receive decisions back, and update Ironclad stages automatically - Track bottlenecks and cycle times in your own analytics without losing Ironclad’s audit trail

eSignature & Post-Execution Obligations

- Initiate signature packets, monitor completion, and distribute executed agreements to stakeholders and iManage - Extract obligations and renewal dates; create tasks in Jira/Asana/ServiceNow and calendar reminders tied to the matter

CRM/ERP-Driven Intake

- Start workflows from Salesforce or procurement systems with prefilled fields - Keep commercial systems updated with status, signed copies, and key terms

Technical Specifications

Authentication

Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials

Response format

JSON with consistent resource schemas and pagination across modules

Rate limits

Tuned for enterprise throughput while honoring customer entitlements and usage controls

Session management

Automatic reauth and cookie/session rotation with health checks

Data freshness

Near real-time retrieval of workflows, contracts, documents, and signature states

Security

Encrypted transport, scoped tokens, and audit logging; respects Ironclad role-based permissions

Webhooks

Optional asynchronous delivery for long-running workflows (e.g., approval transitions, signature completions, bulk imports)

iManage integration

Workspace resolution from matter numbers, profile metadata mapping, and automatic check-in/out supported

Latency

Sub-second responses for list/detail queries under normal load; approval/signature completion times reflect underlying platform behavior

Throughput

Designed for high-volume intake, document versioning, and repository synchronization

Reliability

Retry logic, backoff, and idempotency keys minimize duplicates and support at-least-once processing

Adaptation

Continuous monitoring for UI/API changes with rapid adapter updates

Frequently asked questions

Supergood supports workflows commonly used for CLM, including Workflow Designer & Intake, Negotiation & Redlining (documents/versions), Approvals, Signature Orchestration (Ironclad Sign and leading providers), Repository/Search, and Reporting/Audit—subject to your licensing and entitlements. We scope coverage during integration assessment.

We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling and monitoring for session expiry.

Yes. We can resolve or create iManage workspaces from matter numbers captured in Ironclad, map Ironclad fields to iManage profile metadata, and check in/out versions during negotiation and on execution. Naming standards and folder structures are configurable.

Yes. We can publish approval tasks to collaboration tools, ingest decisions back into Ironclad, initiate signature packets, and track completion via polling or webhooks. All transitions preserve auditability.

We maintain a field mapping layer that standardizes common attributes (e.g., counterparty, effective/renewal dates, amount, governing law) while retaining raw field keys for lossless audit and export.

Yes. We can pull structured terms from the repository or Smart Import, then create tasks and reminders in Jira/Asana/ServiceNow and calendar systems, tied back to the contract and iManage matter.

Ready to get a real API?