Error Handling

​

Error response format

{
  "error": {
    "status": false,
    "type": "invalid_request_error",
    "code": "invalid_request",
    "message": "Invalid parameter: temperature must be between 0 and 2.",
    "msg": "Invalid parameter: temperature must be between 0 and 2.",
    "param": "temperature",
    "traceId": "abc123",
    "retry_after_sec": 30
  }
}

​

Error reference

​

Quick guide

• Fix first, then retry: authentication_error, billing_denied, model_not_found, invalid_request, unsupported_protocol
• Wait, then retry: rate_limit_error — use retry_after_sec or Retry-After when available
• Retry with backoff: service_unavailable and in-stream streaming errors; contact support with traceId if it keeps failing
• Usually ignore: client_aborted
• If code is missing: rely on error.type and the HTTP status
• Still stuck? Contact support with traceId

​

Streaming requests

1. Before any stream data is sent — You get the same JSON error object and a non-2xx HTTP status as in the table above.
2. After the stream has started — HTTP may already be 200. The failure is reported as an error event inside the stream (format depends on the API). The text is usually generic, for example upstream stream error, please retry later. Retry with backoff; if it keeps happening, contact support with traceId.