Cohere API

Cohere API errors and fixes

8 Cohere API errors from the official error docs, grouped by HTTP status, each with what it means, why it happens, the documented fix and whether to retry. Verified October 18, 2026.

Official error docsdocs.cohere.com
Status pagestatus.cohere.com

HTTP 400 Bad Request

400 Bad Request400 responses are sent when the body of the request is not valid. This can happen when required fields are missing, or when the values provided are not valid.Retry? Not stated
400 Bad Request (too many tokens)A 400 Bad Request whose documented example messages begin with "too many tokens", sent when the prompt or requested output exceeds the model's token limits.Retry? Not stated

HTTP 401 Unauthorized

401 Unauthorized401 responses are sent when the API key is missing, invalid or has expired.Retry? Not stated

HTTP 402 Payment Required

402 Payment Required402 responses are sent when the account has reached its billing limit.Retry? Not stated

HTTP 404 Not Found

404 Not Found404 responses are sent when the requested resource is not found. This can happen when the model, dataset, or connector ID is incorrect, or when the resource has been deleted.Retry? Not stated

HTTP 429 Too Many Requests

429 Too Many Requests429 responses are sent when the rate limit has been exceeded. Trial keys are rate limited per endpoint (for example 20 req / min on Chat models) and limited to 1,000 API calls a month.Retry? Yes

HTTP 499

499 Request Cancelled499 responses are sent when a user cancels the request.Retry? Yes

HTTP 500 Internal Server Error

500 Server Error500 responses are sent when there is an unexpected internal server error.Retry? Not stated

Newsletter

One email per week. New model releases, API changes, what broke, and how developers are working around it.