canonical: https://jentic.com/apis/googleapis.com/books # Google Books API The Google Books API gives applications structured access to the Google Books repository, covering volume metadata, full-text search, bookshelves, reviews, and personal library management. It supports public catalog discovery as well as authenticated user-library operations such as bookshelf manipulation, reading position tracking, and offline metadata sync. The API is widely used to build reading apps, library tools, citation utilities, and book recommendation features. ## For AI agents Search Google Books, retrieve volume metadata, and manage authenticated user bookshelves, reviews, and reading positions across 51 endpoints. ## Scope Does not handle full-text book content delivery, ebook DRM, or audiobook streaming - use for catalog metadata search and user bookshelf management only. ## Capabilities - Search the Google Books catalog by title, author, ISBN, or full-text query - Retrieve detailed volume metadata including descriptions, ratings, and preview availability - Manage user bookshelves by adding, removing, and listing volumes per shelf - Track and update a reader's last-read position within a specific volume - Sync offline metadata and dictionary content for reading-app caching - Share and unshare family-library books between Google account members ## Use cases ### Reading App Catalog Search Power a consumer reading app's search experience by querying the Google Books catalog for matches against a user's free-text query, returning titles, authors, cover thumbnails, and preview availability. The Books API exposes the same index that powers books.google.com, so apps avoid building and maintaining their own metadata corpus. Integration is typically a single GET against /books/v1/volumes with a query string. Example prompt: Search /books/v1/volumes for q="isbn:9780547928227" and return the title, authors, and thumbnail URL of the top result. ### Personal Library Management Let users curate their Google Books bookshelves directly from a third-party reading app, supporting add, remove, list, and reorder operations on shelves like Favorites, Reading Now, and To Read. The API authenticates with OAuth 2.0 user credentials and respects existing privacy settings on each shelf. This eliminates the need to duplicate library state in a separate backend. Example prompt: Add the volume id zyTCAlFPjgYC to the authenticated user's bookshelf 3 (Reading Now) using the mylibrary endpoint. ### Citation and Bibliography Tools Build a citation generator that resolves an ISBN or free-text reference to a fully populated bibliographic record including authors, publisher, publication date, page count, and ISBN-10/13 identifiers. Researchers and writers use this to auto-fill citation styles such as APA, MLA, or Chicago without manual entry. One volumes lookup yields enough data to format most major styles. Example prompt: Look up volume metadata for ISBN 9780062316097 and format an APA-style citation from the returned title, authors, publisher, and year. ### AI Agent Reading Assistant via Jentic An AI agent uses Jentic to discover the Books API's search and library operations and acts as a reading concierge - finding next-read recommendations from a user's existing bookshelves, fetching previews, and updating reading position as the user finishes chapters. Jentic isolates the user's OAuth token in its vault so the agent never handles raw credentials. End-to-end integration takes under an hour through Jentic search-load-execute. Example prompt: Through Jentic, search for the books_volumes_list operation, load its schema, and execute a query for q="subject:fantasy" maxResults=10. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /books/v1/volumes | Search the Google Books catalog | | GET | /books/v1/volumes/{volumeId} | Get metadata for a specific volume | | GET | /books/v1/mylibrary/bookshelves | List the authenticated user's bookshelves | | POST | /books/v1/mylibrary/bookshelves/{shelf}/addVolume | Add a volume to a user bookshelf | | POST | /books/v1/mylibrary/bookshelves/{shelf}/removeVolume | Remove a volume from a user bookshelf | | GET | /books/v1/myconfig/getUserSettings | Retrieve the user's Books settings | ## Key resources - **Volumes** — Search and retrieve book metadata and previews - **Bookshelves (mylibrary)** — Manage authenticated user's bookshelves and their volumes - **Family Sharing** — Share and unshare books across a Google family group - **Cloud Loading** — Add, update, and delete user-uploaded books in Google Play Books - **My Config** — Read and update per-user Books settings and download access ## Why Jentic - **Setup:** Wiring the Books API by hand means setting up its Google OAuth 2.0 flow, refreshing scoped access tokens, and separating public catalog search from authenticated bookshelf calls yourself. Through Jentic you install once, import the Books API from the API Directory, store the OAuth credentials once, and your agent calls it. - **Permission scoping:** The bookshelf operations put the shelf in the URL path (/books/v1/mylibrary/bookshelves/{shelf}/addVolume), so a rule can pin your agent to one shelf while it searches volume metadata: it can add and remove volumes on that shelf and nowhere else. You choose the operations it may call, so shelf-wide changes beyond that are not included unless you add them. - **Credential handling:** Your Google OAuth client credentials and user refresh token are stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived scoped access tokens and never sees the raw client secret in its prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search Google Books by isbn' or 'add a volume to my bookshelf', and Jentic returns the matching volumes or bookshelves operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Google Drive API** — Store and share user files, including PDFs and EPUBs alongside Google Books metadata. - **Google Custom Search API** — Generic web search API that can include book results but lacks structured bibliographic fields. - **YouTube Data API** — Surface book-related video content (author talks, reviews) alongside Books metadata. ## FAQ ### What authentication does the Google Books API use? The Books API uses OAuth 2.0 for authenticated user-library operations and accepts an API key for public catalog reads. When called through Jentic, the OAuth token or API key is stored encrypted in your Jentic One instance and the agent receives only scoped access - raw credentials never enter the agent context. ### Can I search for a book by ISBN with the Books API? Yes. Send a GET to /books/v1/volumes with the query parameter q=isbn:9780547928227 (substituting the target ISBN). The response includes the title, authors, publisher, page count, and preview availability of any matching volume. ### What are the rate limits for the Google Books API? Google enforces a default of 1,000 queries per day per project for the Books API, with per-user limits applied on authenticated calls. Higher quota can be requested via the Google Cloud console. Track usage in the API dashboard before scaling integrations. ### How do I add a book to a user's bookshelf through Jentic? Use the Jentic search query "add a book to a Google Books bookshelf" to discover the mylibrary.bookshelves.addVolume operation, load its schema, and execute it with the authenticated user's shelf id and the target volumeId. Run pip install jentic to get started. ### Is the Google Books API free to use? Yes, the Books API is free for the default daily quota. Some operations require an authenticated user (OAuth 2.0) but there is no per-call charge from Google for catalog or library access. ### Can the Books API return full text or only previews? The API returns metadata, snippets, and preview URLs but does not stream full book content. Where the publisher allows, the volume response includes a viewability field and a preview link to books.google.com for in-browser reading. ### Can I limit what my agent is allowed to do with the Google Books API? Yes. Because Jentic One is self-hosted, your own rules decide which Books API operations and credentials the agent may use, so you can grant it read-only catalog search on /books/v1/volumes while withholding any bookshelf write. The bookshelf operations carry the shelf in the URL path, such as /books/v1/mylibrary/bookshelves/{shelf}/addVolume, so a rule can pin the agent to a single shelf where it may add and remove volumes and nowhere else. Operations you do not enable, like removeVolume or changing user settings, stay out of reach until you add them.