Errors and status codes
Error response shape and common failure cases.
Most errors follow the same envelope so clients can handle them consistently.
Prop
Type
{
"status_message": "ACCESS_DENIED",
"status_overview": "failed",
"status_code": 403,
"status_data": {
"reason": "Token does not have access to this resource."
}
}- 401 UNAUTHORIZED: Credentials missing or invalid.
- 403 FORBIDDEN: Token exists but is not allowed.
- 403 ACCESS_DENIED: The user does not own the resource.
- 404 NOT_FOUND: The resource does not exist or is hidden.
- 429 RATE_LIMITED: Too many requests in a short window.
Rate limiting
When you receive a 429, back off and retry with exponential delay. Avoid running parallel retries.