E-Signature
Ironclad
API integration
Ship E-Signature features without building the integration. Full Ironclad API access via Proxy, normalized data through Unified APIs, and 10+ MCP-ready tools for AI agents — all extensible to your exact use case.
Talk to usUse Cases
Why integrate with Ironclad
Common scenarios for SaaS companies building Ironclad integrations for their customers.
Auto-generate contracts from CRM deal data
SaaS companies building CRM or deal management tools can let their users launch Ironclad contract workflows directly from deal records, mapping deal size, customer entity, and line items to the correct workflow schema — eliminating double-entry and reducing cycle times from weeks to days.
Sync contract status into your product in real time
By polling Ironclad workflow states, SaaS platforms can surface granular contract progress (e.g., 'Pending Finance Approval,' 'Out for Signature,' 'Signed') inside their own UI, so end users never have to context-switch to Ironclad to check on a deal or onboarding flow.
Cancel stale workflows automatically on deal or process changes
When a deal is marked 'Closed Lost' or a vendor fails a compliance check, SaaS products can programmatically cancel the associated Ironclad workflow, keeping both systems in sync and preventing legal teams from reviewing contracts that are no longer needed.
Map users and approval groups across systems
SaaS companies offering multi-tenant platforms need to ensure that workflows are launched on behalf of the correct user and routed to the right approval group. Syncing Ironclad's user directory and groups via Truto's Unified User Directory API ensures accurate identity mapping without custom SCIM plumbing.
Power AI contract intelligence with structured workflow data
AI-driven analytics or deal intelligence platforms can pull structured contract attributes — like governing law, payment terms, and renewal clauses — from completed Ironclad workflows, enabling semantic search and Q&A without raw PDF parsing.
What You Can Build
Ship these features with Truto + Ironclad
Concrete product features your team can ship faster by leveraging Truto’s Ironclad integration instead of building from scratch.
One-click contract launch from any record
Query available workflow schemas, dynamically render required fields, and dispatch a new Ironclad workflow asynchronously — all from a button inside your product.
Embedded contract status tracker
Display a live progress indicator showing the current step, status, and assigned approvers for any Ironclad workflow directly within your app's deal, candidate, or vendor record.
Automated workflow cancellation on state change
Trigger Ironclad workflow cancellation with a comment when your product detects a relevant state change like a lost deal, failed compliance check, or withdrawn offer.
User and group directory sync
Continuously sync Ironclad users and groups into your platform so that workflow assignments, approval routing, and audit trails always reference the correct people.
Dynamic schema-driven form mapping
Fetch Ironclad workflow schemas at runtime to auto-map your product's data model to the exact fields each contract template requires, supporting new templates without code changes.
Contract metadata feed for analytics dashboards
Pull workflow attributes and statuses into your analytics layer so customers can build reports on contract cycle time, bottleneck steps, and approval throughput.
SuperAI
Ironclad AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
list_all_ironclad_workflows
Retrieves the workflows in your Ironclad account. Each workflow object in the response includes key details such as the id, title, associated template, current step, status, creation and update timestamps, and information about the workflow creator. It also includes structured schema definitions for all fields used in the workflow, and the attributes object contains the values submitted for the fields in the workflow.
get_single_ironclad_workflow_by_id
Retrieves the data associated with a specific workflow in your Ironclad account. It always requires ID to fetch.
create_a_ironclad_workflow
Use this endpoint to launch a new Workflow asynchronously for non-blocking performance, which is helpful when/if you provide files to the Workflow.
ironclad_workflows_cancel
Cancel a workflow by id in Ironclad. Requires a comment object in the request body. Returns the canceled workflow details including status and cancellation reason.
list_all_ironclad_users
Retrieves all users belonging to organizations to which the authenticated user has membership in a Missive account. The response includes user details such as user ID, name, and email.
get_single_ironclad_user_by_id
Retrieves the information of a single user from your Ironclad account via SCIM. It always requires ID to fetch.
delete_a_ironclad_user_by_id
This endpoint will delete a single user from your Ironclad account. It always requires ID to delete. If the deletion is successful, all active workflows associated with the deleted user should be automatically reassigned to the default user within the admin group.
list_all_ironclad_groups
Retrieves the list of user groups from your Ironclad account via SCIM. The response includes each group's details, such as the group ID, display name, and metadata like the resource type and location URL. The response also contains a list of group members.
get_single_ironclad_group_by_id
Retrieves the information of a single group from your Ironclad account via SCIM. It always requires ID to fetch.
list_all_ironclad_me
Retrieves basic profile information about the authenticated user in Ironclad. The data returned includes the user's ID, email, username, and other profile details, along with the scopes granted to the authorization token.
list_all_ironclad_workflow_schemas
Returns a list of workflow schemas. Each schema specifies the fields used in the workflow's launch form. Use the form query param to specify the launch form.
get_single_ironclad_workflow_schema_by_id
Retrieves a single workflow schema from your Ironclad account. It always requires ID to fetch.
create_a_ironclad_async_workflow
Use this endpoint to launch/create a new Workflow asynchronously for non-blocking performance, which is helpful when/if you provide files to the Workflow.
Why Truto
Why use Truto’s MCP server for Ironclad
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 650+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
Unified APIs
Unified APIs for Ironclad
Skip writing code for every integration. Use Truto’s category-specific Unified APIs out of the box or customize the mappings with AI.
Unified User Directory API
Unified E-Signature API
Documents
The Document object is used to represent documents of e-signature.
Field Groups
Represents a group of fields in an E-Signature.
Fields
Fields represent the attributes defined for various entities in the underlying product. Depending on the underlying product, custom attributes can be defined by a User on various entities like Template, Workflow, etc. is_user_defined attribute within Field can be used to differentiate between custom and system defined Fields.
Groups
The Group object is used to represent collection of Users.
Stages
The stages represent a stage of an opportunity in a workflow.
Templates
The Template object is used to represent templates cofnigured for various entities like Documents, messages, etc.
Users
The User object is used to represents a User
Workflows
The Workflow object is used to represent automations configured in the e-sign application.
How It Works
From zero to integrated
Go live with Ironclad in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Ironclad account
Use Truto’s frontend SDK to connect your customer’s Ironclad account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Ironclad
Truto’s Proxy API is a 1-to-1 mapping of the Ironclad API. You call us, we call Ironclad, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Ironclad’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Ironclad on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
What authentication method does the Ironclad integration use?
Truto handles auth on your behalf. Ironclad's API uses API key (bearer token) authentication. Your end users connect their Ironclad account through Truto's embedded linking flow, and Truto securely manages credential storage and injection for every API call.
What is the difference between the synchronous and asynchronous workflow creation endpoints?
create_a_ironclad_workflow launches a workflow synchronously, which works well for lightweight contracts. create_a_ironclad_async_workflow is non-blocking and better suited for workflows that include heavy attachments or complex templates, returning immediately so your app isn't held up waiting for Ironclad to process the request.
Can I read the specific fields and data submitted in a workflow?
Yes. get_single_ironclad_workflow_by_id returns the workflow's current step, status, associated template, and the structured attributes (data fields) that were submitted at launch or populated during the workflow — giving you granular access to contract metadata.
How does Truto handle pagination when listing workflows or users?
Truto abstracts away Ironclad's API-specific pagination. When you call list_all_ironclad_workflows or list_all_ironclad_users through Truto, pagination is managed automatically so you receive complete result sets without writing cursor or offset logic yourself.
What happens if an Ironclad user is deleted via the API?
You can delete a user by ID using delete_a_ironclad_user_by_id. In Ironclad, when a user is removed, any active workflows they own are typically reassigned according to the account's admin defaults, so contract processes are not orphaned.
Which Unified APIs does the Ironclad integration support?
Ironclad is available through Truto's Unified E-Signature API (covering Workflows, Users, Groups, Documents, Templates, Stages, Fields, and Field Groups) and the Unified User Directory API (covering Users and Groups). This means you can write integration logic once and support Ironclad alongside other e-signature and directory providers.
Ironclad
Get Ironclad integrated into your app
Our team understands what it takes to make a Ironclad integration successful. A short, crisp 30 minute call with folks who understand the problem.
Talk to us