13/08/2026 · Rate limit headers

Rate limit headers: Retry-After and X-Ratelimit-Reset

13/08/2026

We are extending the rate limit information returned by the API. This is an additive change: no limit and no response format changes, it only adds headers.

  • Retry-After on 429 responses. Gives the number of seconds to wait before retrying. Until now 429 responses did not include it and there was no way to know how long the block would last.
  • X-Ratelimit-Reset on every response. UNIX timestamp of the moment the window renews and X-Ratelimit-Remaining returns to its maximum. Together with X-Ratelimit-Remaining it lets you space out requests as you approach the limit, instead of stopping dead or hitting the 429.
HTTP/1.1 429 Too Many Requests
X-Ratelimit-Limit: 80
X-Ratelimit-Remaining: 0
X-Ratelimit-Reset: 1786012860
Retry-After: 37

X-Ratelimit-Reset is an absolute instant, not a countdown: it stays the same across every response in the same window and only moves forward when the quota renews.

The full header table is in Rate limits.

If your client already implemented its own wait after a 429, you can replace it with the Retry-After value. Most HTTP libraries honour it automatically.