Skip to main content
CreatorAudit does not ship official SDKs yet. The API is fully described by an OpenAPI 3 document, so the recommended path is to generate a typed client for your language from that spec.

Get the OpenAPI spec

The spec is downloadable from the API reference, and GET /v2/meta advertises its location so tools can discover it programmatically:
curl https://api.creatoraudit.com/v2/meta
# -> { "data": { "openapi_url": "/v2/openapi.json", "docs_url": "/v2/docs", ... } }
That resolves to:
https://api.creatoraudit.com/v2/openapi.json
GET /v2/meta is unauthenticated, so you can fetch the spec URL before you wire up credentials. The generated client still needs your API key at request time — see Authentication.

Generate a client

Point your generator at the spec URL. A few common options:
openapi-typescript emits types from the spec — pair it with openapi-fetch for a tiny typed client.
npx openapi-typescript https://api.creatoraudit.com/v2/openapi.json \
  -o src/creatoraudit.d.ts
Pin your generator version and regenerate when the spec changes. The spec carries its own version; new fields are additive within v2. See Versioning.

Prefer to write it yourself?

A generated client isn’t required — the API is plain HTTP with a bearer token. If you’d rather call it directly, start from the hand-written examples:

Python

httpx snippets for auth, pagination, and metrics.

TypeScript

fetch-based requests with typed responses.

cURL

Copy-paste requests for every common call.
Building an agent or tool integration? The spec also drives tool generation — see Tool use.