Skip to main content
This page records how composerID publishes into Ironclad: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. Ironclad is a contract lifecycle system of record. composerID launches a Workflow (or writes a Repository Record) of the appropriate type - for example Statement of Work - carrying the canonical decision and the Intent ID, then tracks execution through event webhooks across signature and storage.
Category: Signature & Contract Management. Coverage status: Specification mapped. Vendor documentation: public developer portal.

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

Public API - getting started

Authentication (OAuth 2.0)

Webhooks reference

Create a Record

​
API posture

​
Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
Record types and workflow properties are tenant-configured in Workflow Designer - confirm the SoW/vendor-agreement type keys and property names per tenant via the schema endpoints. API Access is a separately-licensed SKU; regional hosting (na1/eu1) sets the subdomain.

​
Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.