Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Groq API error

Groq API 429 Too Many Requests: what it means and how to fix it

Error message
429 Too Many Requests

Retry? YesLast verified 3 documented fixes3 sources

What it means

Too many requests were sent in a given timeframe. Limits apply at the organization level across RPM, RPD, TPM, TPD, ASH, ASD and, for some organizations, ITPM and OTPM, and whichever threshold is reached first triggers the error. The Python SDK raises RateLimitError and retries it automatically.

Causes

  • Exceeding requests per minute or per day (RPM, RPD)
  • Exceeding tokens per minute or per day (TPM, TPD)
  • Exceeding audio seconds per hour or per day (ASH, ASD)
  • Exceeding separate input or output token per-minute limits (ITPM, OTPM) where configured

How to fix it

  1. Fix 1.

    Implement request throttling and respect rate limits. The retry-after header (in seconds) is set only when a 429 is returned; x-ratelimit-remaining and x-ratelimit-reset headers are always included.

  2. Fix 2.

    The Python SDK retries 429 2 times by default with a short exponential backoff; configure it with max_retries.

    Snippet
    client.with_options(max_retries=5).chat.completions.create(
  3. Fix 3.

    View your exact limits on the console Limits page. Cached tokens do not count toward rate limits. For higher limits, upgrade to the Developer plan, or use Batch and Flex processing.

More Groq API errors

All 14 Groq API errors

HTTP 429 at other providers

Compare 429 across providers

FAQ

What does the Groq API error "429 Too Many Requests" mean?

Too many requests were sent in a given timeframe. Limits apply at the organization level across RPM, RPD, TPM, TPD, ASH, ASD and, for some organizations, ITPM and OTPM, and whichever threshold is reached first triggers the error. The Python SDK raises RateLimitError and retries it automatically.

How do I fix Groq API "429 Too Many Requests"?

There are 3 documented fixes. Start with the first: Implement request throttling and respect rate limits. The retry-after header (in seconds) is set only when a 429 is returned; x-ratelimit-remaining and x-ratelimit-reset headers are always included.

Should I retry Groq 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)), Cohere API (429 Too Many Requests), DeepSeek API (429 - Rate Limit Reached), Gemini API (429 rate_limit_exceeded; 429 quota_exceeded; 429 too_many_requests; 429 RESOURCE_EXHAUSTED), 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 3 sources: Groq API's official docs and official SDK repositories.

Newsletter

Know when the APIs change

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