Rate limit headers (X-RateLimit) in Rest API - Step-by-Step Execution

Concept Flow - Rate limit headers (X-RateLimit)

Client sends API request

↓

Server checks request count

↓

Compare count with limit

↓

Send 429 error

↓

Send rate limit headers

↓

Client receives response with headers

↓

Client reads headers to manage requests

The client sends a request, the server checks if the request count exceeds the limit, then responds with rate limit headers showing usage and limits.

Execution Sample

Rest API

HTTP/1.1 200 OK
X-RateLimit-Limit: 10
X-RateLimit-Remaining: 7
X-RateLimit-Reset: 1680000000

{ "data": "response" }

A server response showing rate limit headers indicating the total limit, remaining requests, and reset time.

Execution Table

Step	Client Request Count	Limit	Condition (Count < Limit)	Action	Response Headers
1	0	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 9, Reset: timestamp
2	1	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 8, Reset: timestamp
3	2	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 7, Reset: timestamp
4	3	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 6, Reset: timestamp
5	4	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 5, Reset: timestamp
6	5	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 4, Reset: timestamp
7	6	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 3, Reset: timestamp
8	7	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 2, Reset: timestamp
9	8	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 1, Reset: timestamp
10	9	10	True	Process request	X-RateLimit-Limit: 10, Remaining: 0, Reset: timestamp
11	10	10	False	Reject request (429)	X-RateLimit-Limit: 10, Remaining: 0, Reset: timestamp

💡 At step 11, request count equals limit, condition is false, so server rejects request with 429 status.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	After 7	After 8	After 9	After 10	Final
Client Request Count	0	1	2	3	4	5	6	7	8	9	10	10
X-RateLimit-Remaining	10	9	8	7	6	5	4	3	2	1	0	0

Key Moments - 2 Insights

Why does the server send X-RateLimit-Remaining as 0 but still reject the request?

At step 11 in the execution_table, the request count equals the limit, so the server rejects the request with status 429 and shows Remaining as 0 to indicate no more requests allowed.

What does the X-RateLimit-Reset header mean?

The X-RateLimit-Reset header shows the time when the rate limit will reset, so the client knows when it can send requests again without being blocked.

Visual Quiz - 3 Questions

Look at the execution_table at step 5. What is the value of X-RateLimit-Remaining?

A 6

B 5

C 4

D 10

💡 Hint

Check the Response Headers column at step 5 in the execution_table.

At which step does the server start rejecting requests?

A Step 10

B Step 9

C Step 11

D Step 12

💡 Hint

Look for the step where Condition (Count < Limit) becomes False in the execution_table.

If the limit was increased to 15, what would happen to X-RateLimit-Remaining at step 10?

A It would be 5

B It would be 0

C It would be 10

D It would be 15

💡 Hint

Use the formula Remaining = Limit - Count from variable_tracker.

Concept Snapshot

Rate limit headers tell clients how many requests they can make.
X-RateLimit-Limit: total allowed requests.
X-RateLimit-Remaining: requests left.
X-RateLimit-Reset: time when limit resets.
Server sends 429 error if limit exceeded.

Full Transcript

This visual shows how rate limit headers work in an API. The client sends requests, and the server counts them. If the count is less than the limit, the server processes the request and sends headers showing the limit, remaining requests, and reset time. When the count reaches the limit, the server rejects further requests with a 429 error but still sends the headers. The X-RateLimit-Reset header tells the client when it can try again. This helps clients avoid sending too many requests and getting blocked.