burst_limit_exceeded
HTTP Status: 429 Too Many Requests
Example response
Retry-After header with the number of seconds left in the current 60-second window, plus X-Burst-Limit and X-Burst-Remaining (0).
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 |
| Pro | 60 |
| Business | 120 |
How to fix
- Wait the
Retry-Afterseconds: The header contains the number of seconds remaining in the current 60-second window. Read it and back off accordingly - 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
Catching this error with the SDKs
Related errors
rate_limit_exceeded- Monthly quota exhausted (different from per-minute burst limits)