Clari Integration Identity and Token Setup

Overview

Establish a dedicated integration identity before building any data flow. Treat Revenue API tokens, ingestion partner keys, and Copilot key/password pairs as separate credentials with separate rotation and revocation paths.

Prerequisites

• Named business owner and technical owner for the integration
• Target surface: Revenue API, v2 ingestion, or Copilot API
• Approved secret manager and a non-production validation boundary

Instructions

Step 1: Choose the surface

Record the exact base URL and authentication contract: Revenue API uses the apikey header, v2 ingestion additionally requires partnerkey, and Copilot uses both X-Api-Key and X-Api-Password.

Step 2: Create a dedicated identity