429 Too Many Requests
The HTTP status meaning the caller has sent too many requests in a given time and should slow down.
In more detail
It is a throttling answer, not a permission refusal like 403. It often carries Retry-After, and the client should still back off with jitter.
Example
In the APIs course: The course service allows two calls per window and then answers 429 with Retry-After: 1.Related terms
- rate limiting — Capping how many requests a client may make in a period of time, and rejecting or delaying the rest.
- Retry-After — The response header that tells a client how long to wait, in seconds or as a date, before trying again.
- backoff — Waiting longer and longer between successive retries, often doubling the delay each time, so a struggling service has room to recover.
- jitter — A random amount added to or taken from a retry delay so that many clients do not all retry at the same moment.
Taught in
- When The Call Fails — AI Engineering: LLM Apps, RAG & Agents
- Retrieval That Finds The Right Thing — AI Engineering: LLM Apps, RAG & Agents
- Rate Limiting Strategies — Modern API Architecture: REST, GraphQL & gRPC
- Rate Limiting And Resource Consumption — Application Security & Threat Modeling for Engineers