OpenAI API error 429 rate limit exceeded

You're getting Error 429: Rate limit exceeded when calling the OpenAI API, and your application just stopped working. This hits developers hardest during production traffic spikes or when testing new features with rapid-

OpenAI API error 429 rate limit exceeded

You're getting `Error 429: Rate limit exceeded` when calling the OpenAI API, and your application just stopped working. This hits developers hardest during production traffic spikes or when testing new features with rapid-fire requests.

What's actually happening

Error 429 means you've sent too many requests to OpenAI's servers in a short time window. The API enforces rate limits on three levels: requests per minute (RPM), tokens per minute (TPM), and requests per day (RPD). When you exceed any of these thresholds, the server blocks your request and returns a 429 status code.

Your exact limits depend on your usage tier. New accounts on the free tier get severely restricted limits—sometimes as low as 3 RPM for GPT-4 models. As you spend more money on the API (tracked cumulatively since account creation), OpenAI automatically bumps you through tiers: $5 spent gets you Tier 1, $50 gets Tier 2, and so on up to Tier 5 at $1,000 spent. Each tier multiplies your allowed requests and tokens.

The error response usually includes headers telling you exactly which limit you hit: `x-ratelimit-limit-requests`, `x-ratelimit-remaining-requests`, and `x-ratelimit-reset-requests`. Check these in your API logs to see whether you're hitting RPM, TPM, or daily limits.

How to fix it

1. Check your current tier and limits

Go to platform.openai.com/settings/organization/limits. This page shows your exact tier and the specific limits for each model you're using. If you're on a low tier, you'll see numbers like "3 requests per minute" for GPT-4 or "200 requests per minute" for GPT-3.5-turbo.

2. Implement exponential backoff

Add retry logic to your code. When you receive a 429 error, wait a few seconds and try again. Double the wait time with each subsequent failure: wait 1 second, then 2, then 4, then 8. Most API libraries support this natively—for the official Python library, use the `max_retries` parameter when creating your client.

3. Add request queuing

If you're making multiple API calls in quick succession, queue them instead. Spread requests across time to stay under your per-minute limits. For Python, you can use libraries like `ratelimit` or build a simple token bucket implementation. The goal is never sending more than your RPM limit within any 60-second window.

4. Increase your tier

The fastest solution is spending more money to reach the next tier. Add credits at platform.openai.com/settings/organization/billing and make some API calls. Your tier updates automatically when your cumulative spending crosses the threshold. You can see detailed tier thresholds and limits at platform.openai.com/docs/guides/rate-limits.

5. Request a limit increase

If you need higher limits than your tier provides, click "Request increase" on the limits page. Fill out the form explaining your use case and required throughput. OpenAI reviews these manually—expect 2-5 business days for a response. They're more likely to approve if you show consistent usage history and have billing in good standing.

If that doesn't work

Check whether you're actually hitting other API errors disguised as rate limits. A 429 can sometimes indicate billing issues rather than true rate limiting. Verify your payment method is valid and you have sufficient credits.

When contacting support, include: your organization ID (from platform.openai.com/settings/organization/general), the exact error message including response headers, timestamps when errors occurred, and your current usage tier. Contact OpenAI support through the help widget in the bottom right of the platform dashboard. Response times average 24-48 hours for Tier 1+ accounts.

Questions people actually ask

Q: Will my tier go down if I stop using the API?

A: No. Usage tiers are based on cumulative lifetime spending. Once you reach a tier, you stay there permanently—even if you don't use the API for months.

Q: Can I pay to instantly get higher limits?

A: Not directly. You must actually spend the money through API usage to advance tiers. Adding $100 in credits doesn't bump your tier—you need to use those credits making API calls.

Q: Does the free trial have separate limits?

A: The $5 free credit for new accounts operates under the same free tier limits as accounts without credits. The free tier restrictions are identical whether you're using free credits or paid ones.

Q: Why am I getting 429 errors with only a few requests?

A: You're likely on the free tier with very low limits (often 3 RPM for GPT-4). Check your tier status—new accounts default to heavily restricted limits until you spend money.

What to remember

  • Error 429 means you exceeded requests per minute, tokens per minute, or daily request limits
  • Your tier determines your limits—check platform.openai.com/settings/organization/limits for exact numbers
  • Implement exponential backoff and request queuing in your code before doing anything else
  • Usage tiers increase automatically as your cumulative spending grows ($5, $50, $500, $1,000)
  • Manual limit increases are possible but require submitting a request form and waiting for approval

---

*openai-support.com is an independent resource, not affiliated with OpenAI Inc.*

Related help