Rate limit headers

Understand how rate limit headers in API responses help you monitor and manage your BookHub API usage.

v2 supports 150 requests per minute (a 60-second window). The API returns a 429 response when you exceed the limit. Each BookHub API response includes the following rate limit headers, helping you monitor your current usage and limit status.

Header Name	Description
X-RateLimit-Limit	The total number of requests allowed in the current time window (e.g., 150).
X-RateLimit-Remaining	The number of requests remaining in the current time window.
X-RateLimit-Reset	The time when the current rate limit window resets, in UTC epoch seconds.

Example response headers

In the following example, you can send up to 150 requests per minute, leaving 120 remaining in the current window.

HTTP/1.1 200 OK
Content-Type: application/json
X-RateLimit-Limit: 150
X-RateLimit-Remaining: 120
X-RateLimit-Reset: 1700000000

When you exceed the limit, the API returns 429 Too Many Requests. The headers show no requests remaining and when the window resets:

HTTP/1.1 429 Too Many Requests
Content-Type: application/json
X-RateLimit-Limit: 150
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1700000060

{
  "status": "error",
  "message": "Rate limit exceeded. Retry after the window resets (see X-RateLimit-Reset header)."
}

See Monitor rate limits for retry guidance.

Next steps

Explore related topics:

How-to guides

• Monitor rate limits — Track your API usage to avoid exceeding rate limits.

---