burst_limit_exceeded
HTTP Status: 429 Too Many Requests
Example response
Retry-After header telling you exactly how many seconds to wait:
What happened?
You’ve sent too many requests in a single minute. Burst limits protect the API from accidental tight loops and misconfigured clients.| Tier | Burst Limit (per minute) |
|---|---|
| Free | 20 |
| Business | 60 |
| Scale | 120 |
How to fix
- Wait the
Retry-Afterseconds — The header tells you exactly when you can retry (1-60 seconds) - Add a delay between requests — Space out your requests to stay within the per-minute limit
- Implement exponential backoff — On 429 responses, wait and retry with increasing delays
- Upgrade your tier — Higher tiers have higher burst limits
Common mistakes
- Tight polling loops — Don’t call the API in a
while(true)loop without delays - Ignoring
Retry-After— Always read this header instead of guessing when to retry - Confusing with
rate_limit_exceeded— Burst limits are per-minute; monthly limits are separate
Related errors
rate_limit_exceeded— Monthly quota exhausted (different from per-minute burst limits)