Errors

Error response format

All error responses follow this structure:

{
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable description of what went wrong",
    "request_id": "req_a1b2c3d4"
  }
}

code -- Machine-readable error code. Use this for programmatic error handling.
message -- Human-readable description. Safe to display to end users.
request_id -- Unique request identifier. Include this when contacting support.

Status	Code	Meaning
`200`	--	Success
`401`	AUTHENTICATION_REQUIRED	Invalid or missing API key
`403`	INSUFFICIENT_PERMISSIONS	No access to requested collection
`404`	NOT_FOUND	Collection not found
`422`	VALIDATION_ERROR	Invalid request body
`429`	RATE_LIMITED	Rate limit exceeded
`500`	INTERNAL_ERROR	Internal server error

401 AUTHENTICATION_REQUIRED -- Check that the Authorization header is present and the key is valid. Keys start with sk_live_.
403 INSUFFICIENT_PERMISSIONS -- The API key doesn't have access to this collection. Use an org-wide key or add the collection to the key's scope.
404 NOT_FOUND -- Verify the collection name exists. Names are case-sensitive.
422 VALIDATION_ERROR -- Check required fields (query is required; exactly one of collection/collections). Ensure query is under 1000 characters and limit is between 1-30.
429 RATE_LIMITED -- Wait for the Retry-After period and implement exponential backoff. See Rate Limits for details.
500 INTERNAL_ERROR -- An unexpected error occurred. Retry the request. If it persists, contact support with the request_id.

Usage is tracked per API key. View statistics on your Usage page in the dashboard.