Protocols
Saved & recent

Rate limiting

Also called: request throttling, API rate limit

Rate limiting controls how much activity a caller may perform over time. An HTTP service can signal a limit with 429 Too Many Requests and may supply Retry-After. The quota might apply to an account, token, address or resource; HTTP does not prescribe a universal counting algorithm.

Imagine an export API allowing an account ten starts per minute. An eleventh request receives 429 with Retry-After: 20, asking the client to wait twenty seconds before trying again. Waiting does not reserve future capacity. Clients also need retry limits and safe retry behavior, because a quota response and an uncertain earlier request are different situations.

Read first
HTTP
Related
Retry backoff and jitter, Idempotency key, Backpressure
Further reading
IETF RFC 6585 — 429 Too Many Requests
hypothetical account quota 1 2 3 4 5 6 7 8 9 10 10 export starts per minute 11 429 Retry-After: 20 eleventh attempt limited 20-second wait another attempt outcome conditional
The eleventh request exceeds this hypothetical account quota. Retry-After: 20 asks the client to wait twenty seconds; it does not promise success or reserve capacity.

View in the full Protocols collection