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
- Further reading
- IETF RFC 6585 — 429 Too Many Requests