Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
The Icertis connector is part of the Integration Hub. It reads agreements from the Icertis Contract Intelligence (ICI) REST API and writes Coverbase’s risk view back as agreement attributes.

​
What it does

The required clause pack is the high and critical clauses of your active clause sets, up to 25, by clause ID and name. Blocking issues are the titles of the vendor’s open findings, up to 20.

​
Authentication

ICI tenants sit behind your identity provider, so the token URL is part of the connection. The grant is OAuth 2.0 client credentials.
  1. In your identity provider, register a client for Coverbase with the client credentials grant and access to the ICI API. Note the token URL, client ID, client secret and any scope it needs.
  2. In Icertis, create agreement attributes for the values Coverbase writes back, for example CoverbaseRiskRating, CoverbaseClausePack and CoverbaseBlockingIssues.

​
Set up in Coverbase

  1. Open Configuration → External Integrations and click Icertis.
  2. On Authentication, enter the Instance URL, Token URL, Client ID, Client secret and, if needed, Scope.
  3. Turn on write-back, set the Sync Interval (Minutes), click Save, then Test connection.
  4. On Field Mappings, check the outbound Target attribute names and Save mappings.
  5. Click Sync now and read the Sync Log.

​
Onboarding checklist

  1. A client in your identity provider, and the token URL.
  2. Agreement attributes for the values Coverbase writes back.

Integration Hub guide

Field mappings and the sync log.

Ironclad

The other contract lifecycle connector.

Contract intake and approval

What happens when a contract is executed.

Integration credentials and signing

How the client secret is kept.