Skip to main content

Error Reference

Error Response Format

Every error follows this shape:
Include request_id when contacting support - it identifies the exact request server-side.

HTTP Status Codes

CodeMeaning
400Bad Request - invalid parameters or body
401Unauthorized - missing or invalid API key
403Forbidden - access denied to resource
404Not Found - resource doesn’t exist
409Conflict - resource already exists / conflicting state
422Unprocessable Entity - request fails schema validation
429Too Many Requests - rate limit or quota exceeded
500Internal Server Error
503Service Unavailable - temporary degradation

Error Codes

bad_request (400)

Invalid request parameters or malformed body. Check required fields and types against the endpoint docs.

unauthorized (401)

Missing or invalid API key.

forbidden (403)

The authenticated organization doesn’t own the requested space or resource.

not_found (404)

Memory, space, or resource doesn’t exist, or the ID is misspelled.

conflict (409)

Resource already exists or is in a conflicting state.

validation_error (422)

Request body fails schema validation - check field types and required parameters.

rate_limited (429)

Rate limit or quota exceeded. Retry with exponential backoff or upgrade your plan.

internal_error (500)

Unexpected server error. Retry, and contact support with the request_id if it persists.

service_unavailable (503)

Temporary degradation. Retry after a short delay.

Retry Strategy

Retry 429, 500, and 503 with exponential backoff:

Handling Errors (Python SDK)

AnonaError has two attributes: .status_code (int) and .detail (the parsed error body, or raw text if not JSON).

Next Steps

API Reference

All API endpoints

Support

Contact support