HTTP 429Rate limit exceeded
rate_limited
The per-key burst window (requests per minute) is exhausted. This is short-term throttling — unlike quota_exhausted, it clears within seconds. The Retry-After header says exactly how long to wait.
This page is where the problem type URI https://usepostify.com/docs/api/problems/rate-limited resolves.
Common causes
- A burst of requests exceeded the key's per-minute limit (30–300/min depending on plan).
- Parallel workers share one key and collectively exceed its window.
- A retry loop without backoff amplifies itself.
How to fix
- Honor Retry-After, then retry — the official SDK does this automatically for safe requests.
- Watch the RateLimit / X-RateLimit-Remaining headers and pace proactively.
- Higher plans get bigger burst windows (see the rate limits table).
Example response
429 · application/problem+json
{
"type": "https://usepostify.com/docs/api/problems/rate-limited",
"title": "Rate limit exceeded",
"status": 429,
"code": "rate_limited",
"detail": "Burst limit reached. Retry after 21 seconds.",
"request_id": "req_6f1f8a2b40d34cd2a6f1e2c9b8d7a601"
}