RateLimit header fields
Response headers that tell a client its rate-limit budget: the limit, how much remains and when it resets.
In more detail
They are hints for pacing, not permission, and the server still enforces the limit. Keep their units and scope consistent so clients can pace themselves without guessing.
Examples
In the APIs course: The IETF is standardising RateLimit and RateLimit-Policy; many services still use the older X-RateLimit-Limit, -Remaining and -Reset, as the course service does.X-RateLimit-Limit: 2X-RateLimit-Remaining: 1Related 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.
- 429 Too Many Requests — The HTTP status meaning the caller has sent too many requests in a given time and should slow down.
Taught in
- Rate Limiting Strategies — Modern API Architecture: REST, GraphQL & gRPC
- Traffic Management: Sliding Window Rate Limiting — Production Full-Stack Engineering