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 Ironclad connector is part of the Integration Hub. It reads Ironclad’s Records API, the repository of agreements, and writes Coverbase’s risk view back onto each record.

​
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, separated by semicolons. Blocking issues are the titles of the vendor’s open findings, up to 20.

​
Authentication

Ironclad uses a bearer API token.
  1. In Ironclad, create an API token with access to records, and note your instance URL.
  2. Create record properties for the values Coverbase writes back, for example coverbaseRiskRating, coverbaseClausePack and coverbaseBlockingIssues.

​
Set up in Coverbase

  1. Open Configuration → External Integrations and click Ironclad.
  2. On Authentication, enter the Instance URL and API token.
  3. Turn on Write risk tier, approval status and contract values back to the provider for two-way sync, set the Sync Interval (Minutes), click Save, then Test connection.
  4. On Field Mappings, check each outbound row’s Target matches your property keys, and Save mappings.
  5. Optionally create a webhook signing secret so Ironclad, through middleware that signs the call, can trigger a sync when a record changes. See Set up the webhook.
  6. Click Sync now and read the Sync Log.

​
Onboarding checklist

  1. An API token and the instance URL.
  2. Record properties for the values Coverbase writes back.
  3. Vendors in Coverbase for the counterparties you contract with, so executed copies file against them.

Integration Hub guide

Field mappings and the sync log.

Icertis

The other contract lifecycle connector.

Contract intake and approval

What happens when a contract is executed.

Clause set library

The clause sets the required clause pack comes from.