request_id when contacting support — it pinpoints the exact request.
Status codes
Validation details
validation_error responses include a details array of field issues:
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Error envelope and status codes.
{
"data": null,
"error": { "code": "forbidden", "message": "Missing required scope: assistants:create" },
"request_id": "0f1c2d3e-..."
}
request_id when contacting support — it pinpoints the exact request.
| Status | error.code | Meaning |
|---|---|---|
400 | validation_error | Request body/params failed validation (see error.details) |
400 | subaccount_required | No subaccount specified or resolvable |
401 | unauthorized | Missing, malformed, expired, or revoked API key; or source IP not allowed |
403 | forbidden | Key lacks the required scope |
403 | subaccount_forbidden | Key is not authorized for the requested subaccount |
404 | not_found | Resource not found within the resolved subaccount |
429 | rate_limited | Burst or daily rate limit exceeded (see Retry-After) |
502 | call_failed / chat_failed | Downstream provider error |
validation_error responses include a details array of field issues:
{
"data": null,
"error": {
"code": "validation_error",
"message": "Request validation failed",
"details": [{ "path": "name", "message": "Required" }]
},
"request_id": "..."
}
