Claude API errors 401, 403, 404, 429: causes and fixes
The most common Claude API errors are 401, 403, 404 and 429. Below are the causes and fixes by status code; they apply to curl, SDKs and tools such as Claude Code, Cline and Cherry Studio. Full error details are in the API reference.
| Status / error | Cause | Fix |
|---|---|---|
401 API_KEY_REQUIRED |
No key sent | Send the key in x-api-key or Authorization: Bearer; in a tool, check that the key field is filled in. |
401 INVALID_API_KEY |
Wrong key | A typo, or extra spaces or quotes. Copy the full key from the console again. |
401 API_KEY_DISABLED |
Key disabled | Enable it in the console or create a new key. |
403 INSUFFICIENT_BALANCE |
Not enough balance | Top up and retry. The console wallet shows balance and spend. |
| 404 | Wrong path or model | The base URL has /v1 where it should not, or lacks it: Anthropic-compatible is https://api.6090ti.com, OpenAI-compatible is https://api.6090ti.com/v1. A wrong model name or one not enabled for the key also gives 404; check with /v1/models. |
| 429 | Too many requests or the upstream is busy | Lower concurrency and retry later; turn on automatic retries in your tool. |
| 5xx | Upstream temporarily unavailable | Retry later; if it persists, send support the request time and model name. QQ user group: 1109931264 |
| Timeout | Very long answer or slow network | Use streaming or raise the tool’s timeout (Claude Code: API_TIMEOUT_MS). |
Checking in order
- Request
https://api.6090ti.com/v1/modelswith curl to confirm the key works and lists models. - Send the simplest message with curl to confirm the base URL and model name.
- If both work but your tool fails, check how the tool expects the base URL (with or without
/v1).
Related: integration guides · FAQ