Skip to main content

Version 2.0 — January 2, 2026

Hit count analytics

The hitCount field indicates how many times customers retrieve a book’s details via the GET /v2/books/{bookId} endpoint. Use hitCount to measure interest in specific titles, such as tracking post-campaign views to assess marketing impact, and make data-driven decisions about inventory and pricing. See Using the hitCount field for analytics, and Rank books by hitCount to find top performers for more details on using this new field.

Deactivate a book

Publishers can now temporarily remove books from the BookHub marketplace without permanently deleting them. Use the PATCH /v2/books/{bookId}/deactivate endpoint to deactivate a book, which changes its status to INACTIVE. Deactivated books are excluded from search results and future queries, but can be reactivated later. A successful deactivation returns 200 OK with the updated book details. For details on using this endpoint, see Deactivate a book.

Delete a book

Publishers can now permanently remove INACTIVE books from the BookHub marketplace using the DELETE /v2/books/{bookId} endpoint. Deleting a book removes it from search results and future queries, reducing catalog clutter. A successful delete returns 204 No Content with no response body. For details on using this endpoint, see Delete a book.

Finalize a book

Publishers can now finalize an INACTIVE as well as a PENDING book to make it visible to customers on the BookHub marketplace. Finalizing an INACTIVE book reactivates a previously deactivated title. Use the PATCH /v2/books/{bookId}/finalize endpoint to change a book’s status from PENDING or INACTIVE to ACTIVE. A successful finalization returns 200 OK with the updated book details. For details on using this endpoint, see Finalize a book.

Breaking changes

See Breaking changes for the full list of v2 breaking changes, including the removal of title sorting, the new Idempotency-Key requirement, and 409 Conflict enforcement for duplicate ISBNs.

Version 1.0 — Initial release

v1 is supported until December 31, 2026. After this date, v1 endpoints will return 410 Gone. Migrate to v2 before the deadline.
The BookHub Publisher API v1 introduced programmatic management of book inventory on the BookHub marketplace, including endpoints for creating, retrieving, and managing books. See Migrate to BookHub Publisher API v2 for details on migrating from v1 to v2.

Next steps

Explore related topics:

Quickstart

  • Quickstart guide — Get up and running with the BookHub Publisher API in minutes.

Conceptual guides

How-to guides

API reference

  • API reference overview — Get an overview of the BookHub Publisher API, including versioning, authentication, available endpoints, and error handling

Reference

  • API endpoints — Explore all available API endpoints and their parameters for BookHub Publisher API v2.
  • Document information — View version, last updated, changelog, and other key information about the BookHub Publisher API documentation.
  • Data models — Explore schema definitions for BaseBook, BookWithAnalytics, Pagination, and Error response objects in the BookHub Publisher API.
  • Code examples — Copy code samples for book creation, sorting by creation date, handling removed title sorting, and tracking performance with hitCount.
  • Breaking changes — Highlights important information about breaking changes in the BookHub Publisher API.

Last modified on July 25, 2026