clari-sdk-patterns
Production-ready Clari API client patterns in Python and TypeScript. Use when building reusable Clari clients, implementing export pipelines, or wrapping the Clari v4 API for team use. Trigger with phrases like "clari API patterns", "clari client wrapper", "clari Python client", "clari TypeScript client".
Best use case
clari-sdk-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Production-ready Clari API client patterns in Python and TypeScript. Use when building reusable Clari clients, implementing export pipelines, or wrapping the Clari v4 API for team use. Trigger with phrases like "clari API patterns", "clari client wrapper", "clari Python client", "clari TypeScript client".
Teams using clari-sdk-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clari-sdk-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clari-sdk-patterns Compares
| Feature / Agent | clari-sdk-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Production-ready Clari API client patterns in Python and TypeScript. Use when building reusable Clari clients, implementing export pipelines, or wrapping the Clari v4 API for team use. Trigger with phrases like "clari API patterns", "clari client wrapper", "clari Python client", "clari TypeScript client".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Clari SDK Patterns
## Overview
Clari has no official SDK -- build typed wrappers around the v4 REST API. These patterns cover the Export API for forecasts, job polling, and data transformation pipelines.
## Prerequisites
- Completed `clari-install-auth` setup
- Python 3.10+ (primary) or TypeScript 5+
## Instructions
### Step 1: Python Client
```python
# clari_client.py
import os
import time
import requests
from dataclasses import dataclass, field
from typing import Optional
@dataclass
class ClariConfig:
api_key: str
base_url: str = "https://api.clari.com/v4"
poll_interval: int = 5
max_poll_attempts: int = 60
class ClariClient:
def __init__(self, config: Optional[ClariConfig] = None):
self.config = config or ClariConfig(
api_key=os.environ["CLARI_API_KEY"]
)
self.session = requests.Session()
self.session.headers.update({
"apikey": self.config.api_key,
"Content-Type": "text/plain",
})
def list_forecasts(self) -> list[dict]:
resp = self.session.get(f"{self.config.base_url}/export/forecast/list")
resp.raise_for_status()
return resp.json()["forecasts"]
def export_forecast(
self,
forecast_name: str,
time_period: str,
types: list[str] = None,
currency: str = "USD",
export_format: str = "JSON",
) -> dict:
payload = {
"timePeriod": time_period,
"typesToExport": types or [
"forecast", "quota", "forecast_updated",
"adjustment", "crm_total", "crm_closed"
],
"currency": currency,
"schedule": "NONE",
"includeHistorical": False,
"exportFormat": export_format,
}
resp = self.session.post(
f"{self.config.base_url}/export/forecast/{forecast_name}",
json=payload,
)
resp.raise_for_status()
return resp.json()
def wait_for_job(self, job_id: str) -> dict:
for attempt in range(self.config.max_poll_attempts):
resp = self.session.get(
f"{self.config.base_url}/export/jobs/{job_id}",
)
resp.raise_for_status()
status = resp.json()
if status["status"] == "COMPLETED":
return status
if status["status"] == "FAILED":
raise ClariExportError(f"Job {job_id} failed: {status}")
time.sleep(self.config.poll_interval)
raise ClariExportError(f"Job {job_id} timed out after {self.config.max_poll_attempts} attempts")
def download_export(self, download_url: str) -> dict:
resp = requests.get(download_url)
resp.raise_for_status()
return resp.json()
def export_and_download(
self, forecast_name: str, time_period: str
) -> dict:
job = self.export_forecast(forecast_name, time_period)
completed = self.wait_for_job(job["jobId"])
return self.download_export(completed["downloadUrl"])
class ClariExportError(Exception):
pass
```
### Step 2: TypeScript Client
```typescript
// clari-client.ts
interface ClariConfig {
apiKey: string;
baseUrl?: string;
pollIntervalMs?: number;
maxPollAttempts?: number;
}
interface ForecastExport {
entries: ForecastEntry[];
}
interface ForecastEntry {
ownerName: string;
ownerEmail: string;
forecastAmount: number;
quotaAmount: number;
crmTotal: number;
crmClosed: number;
adjustmentAmount: number;
timePeriod: string;
}
class ClariClient {
private apiKey: string;
private baseUrl: string;
private pollIntervalMs: number;
private maxPollAttempts: number;
constructor(config: ClariConfig) {
this.apiKey = config.apiKey;
this.baseUrl = config.baseUrl ?? "https://api.clari.com/v4";
this.pollIntervalMs = config.pollIntervalMs ?? 5000;
this.maxPollAttempts = config.maxPollAttempts ?? 60;
}
private async request<T>(path: string, options?: RequestInit): Promise<T> {
const response = await fetch(`${this.baseUrl}${path}`, {
...options,
headers: {
apikey: this.apiKey,
"Content-Type": "text/plain",
...options?.headers,
},
});
if (!response.ok) {
throw new Error(`Clari API ${response.status}: ${await response.text()}`);
}
return response.json();
}
async listForecasts(): Promise<{ forecasts: any[] }> {
return this.request("/export/forecast/list");
}
async exportForecast(forecastName: string, timePeriod: string): Promise<any> {
return this.request(`/export/forecast/${forecastName}`, {
method: "POST",
body: JSON.stringify({
timePeriod,
typesToExport: ["forecast", "quota", "crm_total", "crm_closed"],
currency: "USD",
schedule: "NONE",
includeHistorical: false,
exportFormat: "JSON",
}),
});
}
async exportAndDownload(
forecastName: string,
timePeriod: string
): Promise<ForecastExport> {
const job = await this.exportForecast(forecastName, timePeriod);
const completed = await this.waitForJob(job.jobId);
const resp = await fetch(completed.downloadUrl);
return resp.json();
}
private async waitForJob(jobId: string): Promise<any> {
for (let i = 0; i < this.maxPollAttempts; i++) {
const status = await this.request(`/export/jobs/${jobId}`);
if (status.status === "COMPLETED") return status;
if (status.status === "FAILED") throw new Error(`Job failed: ${jobId}`);
await new Promise((r) => setTimeout(r, this.pollIntervalMs));
}
throw new Error(`Job ${jobId} timed out`);
}
}
```
## Error Handling
| Status | Meaning | Action |
|--------|---------|--------|
| 401 | Invalid API key | Regenerate token |
| 403 | Insufficient permissions | Admin must grant API access |
| 404 | Wrong forecast name | List forecasts first |
| 429 | Rate limited | Back off and retry |
## Resources
- [Clari API Reference](https://developer.clari.com/documentation/external_spec)
- [Clari Community API Guide](https://community.clari.com/product-q-a-6/clari-api-all-you-need-to-know-556)
## Next Steps
Apply patterns in `clari-core-workflow-a` for forecast export pipelines.Related Skills
strategic-clarity
Guided workflow for establishing team identity, boundaries, and strategic clarity. Use when starting a new role, inheriting ambiguity, when a team lacks clear identity, or when you need to define "what we own" vs "what we don't". Triggers include "strategic clarity", "team identity", "new role", "inherited ambiguity", "what does my team own", or "define our boundaries".
exa-sdk-patterns
Apply production-ready exa-js SDK patterns with type safety, singletons, and wrappers. Use when implementing Exa integrations, refactoring SDK usage, or establishing team coding standards for Exa. Trigger with phrases like "exa SDK patterns", "exa best practices", "exa code patterns", "idiomatic exa", "exa wrapper".
exa-reliability-patterns
Implement Exa reliability patterns: query fallback chains, circuit breakers, and graceful degradation. Use when building fault-tolerant Exa integrations, implementing fallback strategies, or adding resilience to production search services. Trigger with phrases like "exa reliability", "exa circuit breaker", "exa fallback", "exa resilience", "exa graceful degradation".
evernote-sdk-patterns
Advanced Evernote SDK patterns and best practices. Use when implementing complex note operations, batch processing, search queries, or optimizing SDK usage. Trigger with phrases like "evernote sdk patterns", "evernote best practices", "evernote advanced", "evernote batch operations".
elevenlabs-sdk-patterns
Apply production-ready ElevenLabs SDK patterns for TypeScript and Python. Use when implementing ElevenLabs integrations, refactoring SDK usage, or establishing team coding standards for audio AI applications. Trigger: "elevenlabs SDK patterns", "elevenlabs best practices", "elevenlabs code patterns", "idiomatic elevenlabs", "elevenlabs typescript".
documenso-sdk-patterns
Apply production-ready Documenso SDK patterns for TypeScript and Python. Use when implementing Documenso integrations, refactoring SDK usage, or establishing team coding standards for Documenso. Trigger with phrases like "documenso SDK patterns", "documenso best practices", "documenso code patterns", "idiomatic documenso".
deepgram-sdk-patterns
Apply production-ready Deepgram SDK patterns for TypeScript and Python. Use when implementing Deepgram integrations, refactoring SDK usage, or establishing team coding standards for Deepgram. Trigger: "deepgram SDK patterns", "deepgram best practices", "deepgram code patterns", "idiomatic deepgram", "deepgram typescript".
databricks-sdk-patterns
Apply production-ready Databricks SDK patterns for Python and REST API. Use when implementing Databricks integrations, refactoring SDK usage, or establishing team coding standards for Databricks. Trigger with phrases like "databricks SDK patterns", "databricks best practices", "databricks code patterns", "idiomatic databricks".
customerio-sdk-patterns
Apply production-ready Customer.io SDK patterns. Use when implementing typed clients, retry logic, event batching, or singleton management for customerio-node. Trigger: "customer.io best practices", "customer.io patterns", "production customer.io", "customer.io architecture", "customer.io singleton".
customerio-reliability-patterns
Implement Customer.io reliability and fault-tolerance patterns. Use when building circuit breakers, fallback queues, idempotency, or graceful degradation for Customer.io integrations. Trigger: "customer.io reliability", "customer.io resilience", "customer.io circuit breaker", "customer.io fault tolerance".
coreweave-sdk-patterns
Production-ready patterns for CoreWeave GPU workload management with kubectl and Python. Use when building inference clients, managing GPU deployments programmatically, or creating reusable CoreWeave deployment templates. Trigger with phrases like "coreweave patterns", "coreweave client", "coreweave Python", "coreweave deployment template".
cohere-sdk-patterns
Apply production-ready Cohere SDK patterns for TypeScript and Python. Use when implementing Cohere integrations, refactoring SDK usage, or establishing team coding standards for Cohere API v2. Trigger with phrases like "cohere SDK patterns", "cohere best practices", "cohere code patterns", "idiomatic cohere", "cohere wrapper".