Bookmode.

The books data API

Every edition of every book, one API.

Canonical metadata for 50M+ editions with works clustering, ratings aggregates, and new-release freshness — built by the maker of Watchmode.

Pre-launch. Waitlist members get early access and launch pricing.

GET /v1/book/9780140328721200 OK · 41ms
Catalog record · 1 of 74 editions
{
  "isbn13": "9780140328721",
  "title": "Fantastic Mr Fox",
  "work": {
    "id": "bm_work_10493",
    "editions": 74,
    "first_published": 1970
  },
  "authors": ["Roald Dahl"],
  "format": "paperback",
  "ratings": {
    "average": 4.08,
    "count": 496104
  }
}

What's in the database

Five layers no other API serves together — starting with the two developers ask for most.

  • Edition ↔ work clustering

    Every printing, translation, and format grouped under one work — the layer nobody else ships

  • Ratings & review aggregates

    Licensed aggregate numbers by API — the signal the world lost when Goodreads closed its API

  • New-release freshness

    ONIX publisher feeds announce titles months before publication

  • Audiobook metadata

    Narrators, runtimes, and editions for the format every other source ignores

  • Covers & identifiers

    ISBN-10/13, LCCN, OCLC, and cross-source identifier graphs with servable cover images

Why book data is stuck in 2020

Goodreads APIShut down December 2020. Keys revoked, apps died.
Open LibraryRefuses commercial load — 1–3 requests/second, no SLA.
Google Books API~1,000 calls/day, and the ToS bars building a database.
ISBNdb19 flat metadata fields. No works clustering, no ratings.
Ingram / BowkerEnterprise contracts from ~$500/month, quote-only.
BookmodeSelf-serve API from $0, works clustering built in, ratings signal restored.

Migrating? Goodreads API alternative · ISBNdb alternative

Be first through the stacks

Early access, launch pricing, and a say in which endpoints ship first.