Developer documentation

Error Handling

Preview API error semantics and safe retry behavior.

Preview

Error format

The preview API uses an application/problem+json-compatible shape with type, title, status, detail, requestId, and optional field errors. Preserve requestId when contacting support.

Retry guidance

  • Do not retry 400 validation errors without changing the request.
  • Refresh or replace credentials after 401; never loop the same token.
  • Resolve authorization after 403; retries alone will not help.
  • Honor Retry-After after 429 and apply exponential backoff with jitter.
  • Retry selected 5xx failures only when the operation is safe or protected by an idempotency key.