Skip to main content
Every /v1 request requires an API key in the Authorization header:

API keys

  • Keys are created in the dashboard (Settings → API Keys) and always start with sk_live_.
  • The full key is shown once at creation. Only a SHA-256 hash is stored; if you lose a key, revoke it and create a new one.
  • The dashboard shows the first 12 characters (sk_live_xxxx) so you can tell keys apart.
  • The number of active keys is limited by your plan (Free: 2, Pro: 5). Revoked keys don’t count against the limit.

Auth errors

Request IDs

Every authenticated response includes an X-Request-Id header (req_<uuid>). Include it when reporting issues.
Treat keys as secrets: use them server-side only, never in client-side code, and rotate them if they leak. Rate limits are enforced per key; see Rate Limits.