Cohere API error
Cohere API 429 Too Many Requests: what it means and how to fix it
429 Too Many RequestsRetry? YesLast verified 3 documented fixes2 sources
What it means
429 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.
Causes
- Past the per minute request limit ("You are past the per minute request limit, please wait and try again later.")
- Trial key call limit ("You are using a Trial key, which is limited to 40 API calls / minute.")
- Trial token rate limit ("trial token rate limit exceeded, limit is 100000 tokens per minute")
How to fix it
- Fix 1.
Wait and try again later, as the documented error messages instruct.
- Fix 2.
Consult the rate limit documentation to understand the limits; upgrade from a Trial key to a Production key with higher rate limits at https://dashboard.cohere.com/api-keys.
- Fix 3.
For a rate limit increase, reach out to support@cohere.com.
More Cohere API errors
HTTP 429 at other providers
Compare 429 across providers429 ThrottlingExceptionRetry? YesAmazon Bedrock429 ModelNotReadyExceptionRetry? YesAmazon Bedrock429 rate_limit_errorRetry? YesAnthropic API429 rate_limit_error (enforced_spend_limit_reached)Retry? NoAnthropic API429 Too Many Requests (Rate limit is exceeded)Retry? YesAzure OpenAI429 Too Many Requests (System is experiencing high demand)Retry? YesAzure OpenAI429 Too Many Requests (temporary rate limit adjustment)Retry? YesAzure OpenAI429 Too Many Requests (token budget exceeded by request parameters)Retry? Not statedAzure OpenAI429 - Rate Limit ReachedRetry? Not statedDeepSeek API429 rate_limit_exceededRetry? YesGemini API429 quota_exceededRetry? YesGemini API429 too_many_requestsRetry? YesGemini API
FAQ
What does the Cohere API error "429 Too Many Requests" mean?
429 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.
How do I fix Cohere API "429 Too Many Requests"?
There are 3 documented fixes. Start with the first: Wait and try again later, as the documented error messages instruct.
Should I retry Cohere API "429 Too Many Requests"?
Yes. The official docs treat this error as retryable.
Which other AI APIs return HTTP 429?
Per their official error docs: Amazon Bedrock (429 ThrottlingException; 429 ModelNotReadyException), Anthropic API (429 rate_limit_error; 429 rate_limit_error (enforced_spend_limit_reached)), Azure OpenAI (429 Too Many Requests (Rate limit is exceeded); 429 Too Many Requests (System is experiencing high demand); 429 Too Many Requests (temporary rate limit adjustment); 429 Too Many Requests (token budget exceeded by request parameters)), DeepSeek API (429 - Rate Limit Reached), Gemini API (429 rate_limit_exceeded; 429 quota_exceeded; 429 too_many_requests; 429 RESOURCE_EXHAUSTED), Groq API (429 Too Many Requests), Mistral API (429 Too many requests), OpenAI API (429 credit_balance_exhausted; 429 Rate limit reached for requests; 429 rate_limit_error slow_down; 429 organization_spend_limit_exceeded; 429 project_spend_limit_exceeded; 429 organization_usage_limit_exceeded), OpenRouter (429 rate_limit_exceeded), Vertex AI (429 RESOURCE_EXHAUSTED; 429 Resource exhausted, please try again later; 429 Too many requests. Exceeded the Provisioned Throughput), xAI API (429 Too Many Requests).
Sources
Last verified against 2 sources: Cohere API's official docs and official SDK repositories.
- docs.cohere.comhttps://docs.cohere.com/reference/errors
- docs.cohere.comhttps://docs.cohere.com/docs/rate-limits
Newsletter
Know when the APIs change
One email per week. New model releases, API changes, what broke, and how developers are working around it.