> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Ironclad

> Ironclad (Signature & Contract Management): the API posture, publish target and field mapping composerID publishes a decision reference through.

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.

<Info>
  Category: Signature & Contract Management. Coverage status: Specification mapped. Vendor documentation: public developer portal.
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                            |
| -------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Authentication       | OAuth 2.0 with scoped tokens (the legacy static API-token bearer was deprecated 22 Nov 2024).                     |
| composerID publishes | Workflow: POST /public/api/v1/workflows                                                                           |
| Intent ID lands on   | `workflow` `properties.intentId`, written into the destination record                                             |
| Back-sync            | Webhooks: the destination pushes events; composerID verifies each delivery and lands it on the intent's timeline. |

## Vendor documentation

<Columns cols={2}>
  <Card title="Public API - getting started" icon="external-link" href="https://developer.ironcladapp.com/reference/getting-started-api" horizontal />

  <Card title="Authentication (OAuth 2.0)" icon="external-link" href="https://developer.ironcladapp.com/reference/authenticate-a-request" horizontal />

  <Card title="Webhooks reference" icon="external-link" href="https://developer.ironcladapp.com/reference/webhooks" horizontal />

  <Card title="Create a Record" icon="external-link" href="https://developer.ironcladapp.com/docs/create-a-record-1" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                                       |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Authentication | OAuth 2.0 with scoped tokens (the legacy static API-token bearer was deprecated 22 Nov 2024). SCIM 2.0 for provisioning. API Access is a paid add-on/SKU.                                                    |
| Style          | REST, JSON; OpenAPI 3.1                                                                                                                                                                                      |
| Base URL       | https\://\{subdomain}.ironcladapp.com/public/api/v1  (regional na1 / eu1; plus preview and demo)                                                                                                             |
| Webhooks       | Event webhooks - workflow\_launched, workflow\_completed, workflow\_signature\_packet\_fully\_signed, workflow\_attribute\_updated and more; up to 10 retries over \~13.6h; a 410 disables the subscription. |
| Events posture | Webhooks                                                                                                                                                                                                     |
| Rate limits    | Documented CLM API rate limits per plan; standard 429 backoff.                                                                                                                                               |
| Objects        | workflows, records (repository), entities, signature packets, webhooks; a Record has type (e.g. Statement of Work), name, properties\{}                                                                      |

## 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.

<AccordionGroup>
  <Accordion title="Workflow" icon="arrow-right-left" description="Launch a contract process">
    | Mapping                  | Detail                                                                           |
    | ------------------------ | -------------------------------------------------------------------------------- |
    | Canonical to destination | workflow type, counterparty, service\_category, budget, dates                    |
    | Target                   | POST /public/api/v1/workflows                                                    |
    | Requirement              | Required                                                                         |
    | Notes                    | Workflow type maps to the SoW / vendor-agreement process; fetch the schema first |
  </Accordion>

  <Accordion title="Record" icon="arrow-right-left" description="Write a repository record">
    | Mapping                  | Detail                                                                         |
    | ------------------------ | ------------------------------------------------------------------------------ |
    | Canonical to destination | type = Statement of Work, name, properties\{start\_date, cost\_center, budget} |
    | Target                   | POST /public/api/v1/records                                                    |
    | Requirement              | Tenant                                                                         |
    | Notes                    | Use when writing a completed contract straight to the Repository               |
  </Accordion>

  <Accordion title="Intent ID correlation" icon="arrow-right-left" description="Carry the Intent ID">
    | Mapping                  | Detail                                                          |
    | ------------------------ | --------------------------------------------------------------- |
    | Canonical to destination | intent\_id, intent\_version                                     |
    | Target                   | workflow/record property                                        |
    | Requirement              | Required                                                        |
    | Notes                    | Property defined in Workflow Designer; drives webhook back-sync |
  </Accordion>
</AccordionGroup>

<Note>
  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.
</Note>

## Next steps

<Columns cols={3}>
  <Card title="How composerID connects" icon="plug-zap" href="/guides/connect">
    The five ways composerID reaches a destination, and the minimum a destination must offer.
  </Card>

  <Card title="Publishing" icon="send" href="/concepts/publishing">
    Plan, preflight and publish: how a decision becomes a valid record in a destination.
  </Card>

  <Card title="All destinations" icon="plug" href="/destinations">
    Every destination composerID documents, with its category and coverage status.
  </Card>
</Columns>