Skip to main content
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.
Category: Signature & Contract Management. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation).

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

Icertis API Developer Experience

ICI Business APIs overview

Contract Types & Attributes

Obligation Management

​
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.
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).

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