Typed Clari REST Client Patterns

Overview

Wrap only the endpoints the application owns instead of inventing a broad unofficial SDK. Keep Revenue, v2 ingestion, and Copilot clients separate so their base URLs, headers, limits, schemas, and mutation policies cannot bleed across boundaries.

Prerequisites

• Endpoint inventory and pinned first-party contract fingerprint
• Language-native HTTP and schema-validation libraries
• Defined timeout, retry, logging, and secret-redaction policies

Instructions

Step 1: Split clients by surface

Create separate Revenue, ingestion, and Copilot transports with immutable base URLs and header builders.

Step 2: Model request and response types