X-WS-RateLimit-Remaining
The HTTP X-WS-RateLimit-Remaining response header is an unofficial header used by WordPress.com infrastructure to communicate the number of API requests still available in the current rate limit window.
Note
The X- prefix for non-standard headers is
deprecated per RFC 6648.
Usage
WordPress.com enforces rate limits on requests made to its platform. The X-WS-RateLimit-Remaining header reports how many requests are left in the current window before the limit is reached. The value counts down with each request, giving API clients a way to monitor their consumption in real time.
The header appears alongside X-WS-RateLimit-Limit, which shows the total ceiling for the window. Reading both headers together reveals both the budget and the remaining balance. When the remaining value reaches zero, WordPress.com begins throttling or rejecting further requests until the window resets.
This header follows the same pattern as the widely
adopted X-RateLimit-Remaining,
scoped to WordPress.com's infrastructure with the
WS- prefix.
Values
Numeric countdown
The value is a non-negative integer decrementing
with each request. The counter starts near the limit ceiling
and counts down toward zero as requests consume the
available budget. Values like 993, 989, and 999
are common in active sessions.
Example
A response early in a session shows most of the budget intact. The client has made seven requests against a limit of 1,000.
X-WS-RateLimit-Remaining: 993
Both headers typically appear together, showing the full picture of the client's current rate limit status.
X-WS-RateLimit-Limit: 1000
X-WS-RateLimit-Remaining: 989
A session with more activity shows a lower remaining count. The client is still within its budget.
X-WS-RateLimit-Remaining: 751
Takeaway
The X-WS-RateLimit-Remaining header shows how many
requests remain in the current rate limit window on
WordPress.com infrastructure. The value decrements with
each request and pairs with X-WS-RateLimit-Limit to
give clients a complete view of their consumption.