Skip to main content
All v2 error responses use the same response envelope as success responses. This makes error handling consistent and predictable.

Basic Pattern

  1. Check success — if false, the request failed
  2. Read errorCode — use this for programmatic logic
  3. Never parse message — it is human-readable and may change without notice

HTTP Status Categories

Retry Strategy

  • Only retry 429 and 500 errors
  • Never retry 400, 401, 402, or 403 — these require a change in the request or account
  • For 429, use the Retry-After response header (value in seconds)
  • For 500, use exponential backoff (1s, 2s, 4s, max 3 retries)

Full Error Code Reference

See Error Codes for the complete list of all error codes with descriptions and recommended actions.