Skip to main content
HTTP status codes show the broad reason a request failed. When you see 500, 503, 429, or a similar status in an API call, third-party client, or Conversation, start with the status code, then cross-check the failed record in Usage.

Common statuses

Troubleshooting order

  1. Confirm whether the failure happened in Conversation, an API call, or a third-party client.
  2. Check the HTTP status code and returned error message.
  3. Open Usage and find the failed record from the same time range.
  4. Compare the Base URL, model name, request body, key status, balance, and limits against the table above.
  5. If the same request keeps failing, retry with a shorter input or simpler parameters, then switch models to check whether it is a model availability issue.
Do not send full API keys, passwords, or sensitive business data to support. If a key is needed for identification, share only a few leading and trailing characters.

What to include when contacting support

  • Failure time and approximate time zone.
  • Entry point: Conversation, API call, Cursor, Claude Code, Codex, or another client.
  • HTTP status code, such as 500, 503, or 429.
  • Model name, endpoint path, and Base URL.
  • Returned error message or screenshot.
  • Failed record information from Usage.
  • Request ID, if the response includes one.