Skip to main content
All errors follow a consistent JSON format with a machine-readable code and human-readable message.

Error response format

Always include the request_id when contacting support about a failed request. It allows the team to trace the exact request through the system.

Error Handling Decision Tree

Use this diagram to determine the correct recovery strategy for each error class:
Do not retry 4xx errors (except 429). These indicate a problem with the request itself — retrying the same request will always fail. Fix the issue first.

HTTP status codes

Error codes

For 429 errors, see the Rate Limiting guide for retry logic examples with exponential backoff.

Handling errors

Last modified on March 4, 2026