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

# Icertis

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

This page records how composerID publishes into Icertis: 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.

Icertis Contract Intelligence (ICI) is an enterprise CLM system of record. composerID files a Contract Request / Agreement of the appropriate Contract Type, populating attributes from the canonical decision and linking the Compliance File as an Associated Document, with the Intent ID stored as an attribute for correlation.

<Info>
  Category: Signature & Contract Management. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation).
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                                                                             |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Authentication       | OAuth 2.0 via your IdP (Azure AD / Okta / Ping) using OIDC discovery - ICI has no native credential store; calls also carry an ici-product-key (subscription key). |
| composerID publishes | Contract Request: ICI Business API - create Contract Request                                                                                                       |
| Intent ID lands on   | `agreement` `attributes.intent_id`, written into the destination record                                                                                            |
| Back-sync            | Webhooks and polling: some lifecycle events are pushed, the rest are read on a schedule.                                                                           |

## Vendor documentation

<Columns cols={2}>
  <Card title="Icertis API Developer Experience" icon="external-link" href="https://developer.icertis.com/" horizontal />

  <Card title="ICI Business APIs overview" icon="external-link" href="https://www.icertis.com/research/blog/api-clm-value/" horizontal />

  <Card title="Contract Types & Attributes" icon="external-link" href="https://developer.icertis.com/" horizontal />

  <Card title="Obligation Management" icon="external-link" href="https://developer.icertis.com/" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                                                       |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | OAuth 2.0 via your IdP (Azure AD / Okta / Ping) using OIDC discovery - ICI has no native credential store; calls also carry an ici-product-key (subscription key). ICMAuthToken is test-only; Client Certificate on request. |
| Style          | REST, JSON; 200+ Business APIs with standard CRUD                                                                                                                                                                            |
| Base URL       | Region-specific ICI Developer Experience gateway; \{customerinstance}.icertis.com                                                                                                                                            |
| Webhooks       | Rule/event-driven notifications plus async delivery for long-running actions (AI clause extraction, multi-step approvals); poll the GET endpoints where webhooks are not configured.                                         |
| Events posture | Webhooks and polling                                                                                                                                                                                                         |
| Rate limits    | Per-tenant platform limits; long-running operations are asynchronous with status polling.                                                                                                                                    |
| Objects        | Agreements, Contract Types (Contract Request / Agreement / Associated Document / Masterdata), Attributes, Clauses, Templates, Masterdata, Obligations & Fulfillments, Associations                                           |

## 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="Contract Request" icon="arrow-right-left" description="Assemble inputs for an agreement">
    | Mapping                  | Detail                                                             |
    | ------------------------ | ------------------------------------------------------------------ |
    | Canonical to destination | contract\_type, requestor, service\_category, dates, budget        |
    | Target                   | ICI Business API - create Contract Request                         |
    | Requirement              | Required                                                           |
    | Notes                    | Contract Type is tenant-defined; attributes drive the request form |
  </Accordion>

  <Accordion title="Agreement" icon="arrow-right-left" description="Create the executable contract">
    | Mapping                  | Detail                                                      |
    | ------------------------ | ----------------------------------------------------------- |
    | Canonical to destination | attributes\{title, counterparty, effective\_date}, template |
    | Target                   | ICI Business API - create Agreement                         |
    | Requirement              | Tenant                                                      |
    | Notes                    | Uses tenant Templates + Clauses; own vs third-party paper   |
  </Accordion>

  <Accordion title="Intent ID + evidence" icon="arrow-right-left" description="Correlate and attach">
    | Mapping                  | Detail                                                      |
    | ------------------------ | ----------------------------------------------------------- |
    | Canonical to destination | intent\_id (attribute), defence\_file (Associated Document) |
    | Target                   | Agreement attribute + Associated Document                   |
    | Requirement              | Required                                                    |
    | Notes                    | Associated Documents carry the SoW draft / questionnaires   |
  </Accordion>
</AccordionGroup>

<Note>
  ICI is deeply configuration-driven: Contract Types, Attributes, Templates and Clauses are defined per tenant, so mapping needs the tenant's Contract Type schema. Business APIs are a separate SKU and require the APIM Dev Portal role plus an ici-product-key. Auth federates to the customer's IdP (Azure-native).
</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>