Errors and Rate Limits
Error envelope
details is present only on validation errors. Error messages never contain call content, storage paths or internal identifiers.
Error codes
Rate limits
Limits are applied per API key and per minute, with a sliding window:
Responses carry X-RateLimit-Limit and X-RateLimit-Remaining. A 429 response also carries Retry-After (seconds) and retry_after_seconds in the body.
Retry guidance
429→ waitRetry-Afterseconds, then retry.503,500, network errors → exponential backoff starting at 2 seconds, at most 5 attempts.400,401,403,404→ do not retry without changing the request.- All endpoints are read-only; retrying never creates duplicate data. A truncated recording download can be resumed with a
Rangeheader.
Caching and transport
Every response is served over TLS with Cache-Control: no-store. Do not cache transcripts or recordings in shared caches, and store the API key in a secret manager — never in client-side code or URLs.
