Skip to main content
Monitor rate limit headers in API responses to avoid exceeding the BookHub Publisher API limit of 150 requests per minute. Exceeding the limit returns a 429 Too Many Requests response.

Prerequisites

Before you begin, ensure you meet the following prerequisites:
  • Familiarity with BookHub Publisher API v2.
  • A valid JWT for authentication.
  • Access to your codebase that integrates with the BookHub Publisher API.

Step 1: Track rate limit headers

Every API response includes three rate limit headers: X-RateLimit-Limit (the ceiling), X-RateLimit-Remaining (requests left in the window), and X-RateLimit-Reset (the Unix timestamp when the window resets). For details on each header, see Rate limit headers. Add a rate limit check to your API calls:

Step 2: Handle 429 responses

When you exceed the rate limit, the API returns 429 Too Many Requests. Implement retry after the reset window to retry automatically:

Step 3: Test your implementation

Make a request and verify the rate limit headers are present in the response:
Confirm the response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. The X-RateLimit-Reset value is a Unix timestamp — convert it to a human‐readable time if needed:

Response

A 429 Too Many Requests response indicates the rate limit has been exceeded:
The response also includes the rate limit headers so you can calculate when to retry.

Next steps

Explore related topics:

Reference

  • API endpoints — Explore all available API endpoints and their parameters for BookHub Publisher API v2.
  • Rate limit headers — Details on the rate limit headers included in API responses.
  • Error codes — Complete list of error codes including 429.

How to guides


Last modified on August 18, 2026