Documentation
Errors
Standardized error envelopes across gateway endpoints.
Error format
Gateway errors return a JSON payload with an error code and a human-friendly message. Additional fields like fields, errors, or metadata provide context.
{
"error": "MISSING_REQUIRED_FIELDS",
"message": "Missing required fields: input.text",
"fields": ["input.text"],
"metadata": {
"title": "Missing required fields"
}
}Common errors
| Code | Meaning | Status |
|---|---|---|
| NO_TOKEN | Authentication required. Missing or malformed credentials. | 401 |
| TOKEN_INVALID | Invalid client ID or secret. | 401 |
| ACCESS_DENIED | Missing required feature or scope. | 403 |
| RATE_LIMITED | Request or concurrent stream limit exceeded. | 429 |
| USAGE_LIMIT_REACHED | Monthly token quota exceeded. | 403 |
| MISSING_REQUIRED_FIELDS | Payload is missing required fields. | 400 |
| VALIDATION_ERROR | Payload failed validation. | 400 |
| SERVICE_UNAVAILABLE | Upstream service unavailable. | 503 |
Was this page helpful?