Free Book APIs in 2026 — Compared
Five providers, none needing a credit card. Four need no key at all.
For open metadata and covers: Open Library (no key, full dumps). For search quality: Google Books (keyless works, but register a key). For definitions: Free Dictionary API. For synonyms, rhymes and word games: Datamuse (100,000 req/day). For the actual text of public-domain books: Gutendex.
Books are one of the healthier free-API categories: the two heavyweights are backed by the Internet Archive and Google respectively, both have survived a decade, and neither has tightened its terms recently. What the category lacks is the thing people most often want — reviews and ratings — and no amount of stitching free endpoints together produces them. Everything below is in the books API category, checked hourly; our methodology explains what those checks measure.
Comparison
| API | Data | Free tier | Auth | Rate limit | Best for |
|---|---|---|---|---|---|
| Open Library | Book metadata | Free, no key; monthly full dumps | None | Around 100 requests per 5 minutes per IP; covers host budgeted separately | Open metadata and covers |
| Google Books | Book metadata | Keyless works; free key gives 1,000 req/day | None, or free key (recommended) | Per-IP when keyless; 1,000/day per project with a key | Search and disambiguation |
| Free Dictionary API | Definitions | Free, no key, no SLA | None | Unpublished — cache aggressively and degrade gracefully | Definitions and pronunciation |
| Datamuse | Word relations | Free, no key, 100,000 req/day | None | 100,000/day per IP, fast enough to hang off a keystroke | Synonyms, rhymes, word games |
| Project Gutenberg (Gutendex) | Full texts | Free, no key, full public-domain texts | None | Unpublished courtesy limit — do not crawl the text mirrors | Public-domain full texts |
The Goodreads-shaped hole
Goodreads closed its public API in December 2020 and nothing replaced it. That single event is why half the book-API tutorials on the web point at dead endpoints, and why Open Library inherited the traffic: it was the only open, unmetered, ISBN-addressable catalog left standing. What did not transfer was the social layer — reviews, star ratings, shelves and recommendations, which were the reason most people integrated Goodreads in the first place. No free API serves those at anything close to that scale today. Plan around the absence rather than hunting for a substitute that does not exist.
The providers
1. Open Library
Free tier: Free, no key, no signup. Internet Archive backed, with monthly full-catalog dumps
Coverage: 20 million-plus book records, authors, subjects, editions, and hotlinkable covers by ISBN, OLID or LCCN
Auth: None
Rate limit: Around 100 requests per 5 minutes per IP; covers host budgeted separately
Best for: Reading trackers, library tools, ISBN enrichment, open licensing
The open-data default, and the one to reach for when licensing matters or you want the catalog locally. Set generous timeouts: responses genuinely take one to three seconds, and a two-second client timeout makes a working integration look broken. Use the fields parameter to request only what you render — roughly ten times smaller payloads and about half the latency. The deeper trap is identity: OLID, ISBN and LCCN do not cross-reference cleanly, and a work can carry an OLID with no ISBN attached, so a pipeline keyed on ISBN alone silently drops records. Resolve to OLID early and keep it as your internal key. Covers live on covers.openlibrary.org, a separate host with its own rate limit, and a cover-by-ISBN request for a book with no cover returns a 1x1 transparent pixel with HTTP 200, not a 404 — append ?default=false to get a real 404 you can catch.
2. Google Books
Free tier: Search works with no key. A free key moves you from a shared per-IP pool to a per-project 1,000 requests/day quota
Coverage: Roughly 40 million volumes with bibliographic metadata, categories, page counts, publisher data, thumbnails and preview links
Auth: None, or free key (recommended)
Rate limit: Per-IP when keyless; 1,000/day per project with a key
Best for: Search boxes, disambiguation, ISBN enrichment, citation tooling
The fastest book lookup to prototype, and noticeably better than Open Library at fuzzy title matching and publisher metadata. Register a key anyway: keyless quota is enforced per IP, and on cloud infrastructure that IP is shared with every other tenant, so 429s show up at volumes that would never trip a per-project limit. Two data traps follow. totalItems is an estimate, not a count — identical requests seconds apart return different values, so never render it as a result count or derive page counts from it; page until the items array comes back empty. And ISBN search needs the field prefix: a bare number runs a keyword search and returns noise, while isbn:9780261102217 is an exact lookup. The same goes for intitle: and inauthor:. Everything under volumeInfo is optional and publishedDate is variable-precision, so parse it defensively.
3. Free Dictionary API
Free tier: Free, no key. Community-run on donated infrastructure with no SLA
Coverage: Definitions grouped by part of speech, phonetics, audio pronunciation URLs, synonyms, antonyms and examples, sourced from Wiktionary
Auth: None
Rate limit: Unpublished — cache aggressively and degrade gracefully
Best for: Vocabulary apps, tap-to-define reading tools, casual word validation
The only no-key dictionary endpoint worth using, and the natural companion to a reading app. A word that is not found returns HTTP 404 with a JSON error body rather than an empty array, so word-game code asking is this a valid word should treat 404 as no and anything else non-200 as a retry. Audio URLs are present for common words but frequently missing for rarer ones, so guard the field before rendering a play button. This is a volunteer project that has had multi-hour outages, and definitions never change — cache forever. Coverage is Wiktionary's: strong for standard English, patchy for slang and recent coinages.
Free Dictionary API docs ↗ · Live status and integration notes
4. Datamuse
Free tier: Free, no key, 100,000 requests/day per IP
Coverage: Means-like, sounds-like and spelled-like queries with wildcards, plus relation constraints for rhymes, antonyms and related words
Auth: None
Rate limit: 100,000/day per IP, fast enough to hang off a keystroke
Best for: Autocomplete, crossword and word-game helpers, songwriting tools, query expansion
Not a dictionary — a retrieval engine for the question of what word goes here, and unusually good at it. Three limits shape how you query. The max parameter caps at 1000 and defaults to 100; asking for more does not error, it silently returns 1000, and there is no pagination, so broadening a result set means varying constraints rather than paging. Constraints intersect, and an over-constrained query returns an empty array with HTTP 200 rather than an error, with no signal about which constraint killed it — build queries one constraint at a time and treat empty as a cue to relax one. And the daily budget is per IP with no dashboard, so on shared hosting or serverless you are pooling with other tenants. Use the score field for ordering within one query only; it is unnormalized across queries.
5. Project Gutenberg (Gutendex)
Free tier: Free, no key. Gutendex is a community-run JSON wrapper over the Project Gutenberg catalog
Coverage: 70,000-plus public-domain books with metadata, subjects, languages, and direct links to plain text, EPUB and HTML
Auth: None
Rate limit: Unpublished courtesy limit — do not crawl the text mirrors
Best for: E-reader apps, full-text search over classics, NLP corpora
The only entry here that gives you the actual book rather than metadata about it. Project Gutenberg's own site is not a JSON API, so Gutendex exists as a thin searchable layer: query by title, author, language, subject or Gutenberg ID and get back a formats object with download URLs. Everything is public domain, so there are no licensing questions for full-text search, e-reader projects or NLP corpora. The formats object varies by book, so pick a format by inspecting the keys rather than assuming plain text exists — and mirror the catalog rather than pulling texts through repeatedly if you want more than a handful.
Where the free tier genuinely is not enough
If your product depends on ratings, reviews, or bestseller and sales-rank signals, the free tier will not get you there — not by combining endpoints, not by scraping, not by waiting. That data is commercial and licensed, and the honest options are paying for a feed, partnering with a retailer, or building your own review corpus from your own users.
Two patterns that work
Search with Google, store with Open Library. Send the user's messy query to Google Books with the right field prefix and use the top result only to extract an ISBN. Then fetch the canonical record from Open Library, resolve it to an OLID, and store that as your internal book key. You get Google's matching quality on the way in and Open Library's licensing and covers for everything you persist.
Reading tool with a word layer. Pull public-domain texts from Gutendex, wire tap-to-define to the Free Dictionary API behind a permanent local cache, and use Datamuse for the vocabulary features around it. None of the three needs a key, so the stack runs with zero credential management.
Frequently Asked Questions
What is the best free book API?
Google Books for search and Open Library for everything else, used together. Google Books has better fuzzy title matching and publisher metadata, so use it to turn a messy query into an ISBN. Open Library has open licensing, hotlinkable covers, downloadable dumps and no quota, so use it to enrich and store that ISBN. Running both is the normal pattern, not a compromise.
Do I need an API key for the Google Books API?
No, search works with no key — but register one anyway. Keyless quota is enforced per IP, and on cloud hosting that IP is shared with every other tenant, so 429s appear at volumes that would never trip a real limit. A free key gives you a per-project quota of 1,000 requests a day that you actually control.
What replaced the Goodreads API?
Nothing did. Goodreads closed its public API in December 2020 and no equivalent replacement appeared. Open Library became the practical fallback for book metadata, covers and subject data, and it is what most former Goodreads integrations migrated to. Ratings and reviews at Goodreads scale are simply not available from a free API any more.
Is there a free API for book covers?
Open Library serves hotlinkable covers by ISBN, OLID or LCCN from covers.openlibrary.org, with no key. Watch one behaviour: when no cover exists the endpoint returns a 1x1 transparent pixel with HTTP 200, not a 404, so a naive integration renders an invisible image instead of your placeholder. Add default=false to get a real 404 you can catch.
Is there a free API for full book texts?
Yes, for public-domain works. Gutendex wraps the Project Gutenberg catalog in JSON and links directly to plain text, EPUB and HTML downloads for 70,000-plus titles, with no key. Anything still in copyright is out of reach — Google Books exposes full-text search inside some in-copyright volumes where the publisher permits it, but never the text itself.
Can I get book ratings and reviews from a free API?
Not at any useful scale, and this is the real gap in the category. Since Goodreads closed its API there has been no free source for current commercial book reviews or aggregate ratings. Open Library exposes reading-log counts and some ratings, but the volume is a fraction of Goodreads and thin for recent titles.
Related on FreeAPI.watch
- Book API live status — hourly checks for every API on this page
- Free APIs with no API key — broader list of no-signup endpoints
- Free recipe & nutrition APIs — the same treatment for food data
- How we measure free-tier quality — the score behind our rankings
Last reviewed: August 2026. Terms verified against each provider's documentation.