Nytimes Books API

Name: Books API
Brand: Books API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey7 EndpointsREST

Install Jentic One Beta

Connect the Books API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Books API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Books API.

Retrieve a Best Sellers list for a given date and list name

Pull the full overview of every Best Sellers list in a single call

Fetch the trimmed top-5 overview snapshot across all active lists

Enumerate every available Best Sellers list with publication frequency

GET STARTED

Start building with Books API

Explore with Jentic

View OpenAPI Document

For Agents

Pull NYT Best Sellers rankings, full overview snapshots, list metadata, book ranking history, and critic reviews via 7 GET endpoints.

Use for: Get the current NYT hardcover fiction Best Sellers list, Pull every Best Sellers list in one full overview call, Find the bestseller history for a book by ISBN, Retrieve every NYT Best Sellers list category

Not supported: Does not handle book purchases, e-book downloads, or general article search - use for NYT Best Sellers rankings, list overviews, and critic book reviews only.

Use Cases

Patterns agents use Books API for, with concrete tasks.

★ Cross-List Best Sellers Dashboard

Build a dashboard that shows every active NYT Best Sellers list at full depth in a single load. The /lists/full-overview.json endpoint returns the complete ranked entries across every list rather than just the top five returned by the standard overview endpoint, letting consumers display all 50+ lists without making per-list requests.

Call /lists/full-overview.json and group the results by list name to render a tabbed dashboard with full rankings per list.

Book Ranking History Lookup

Power a book detail page that shows a title's full NYT Best Sellers ranking history. The /lists/best-sellers/history.json endpoint accepts isbn, author, title, or publisher and returns every list appearance with weeks-on-list and rank progression, enabling rich book-detail visualisations.

Call /lists/best-sellers/history.json?isbn=9780525559474 and chart the rank-last-week values over weeks-on-list to produce a ranking trajectory.

Editorial Review Aggregation

Aggregate NYT critic reviews for a book detail page or recommendation feed. The /reviews.json endpoint accepts isbn, title, or author and returns review metadata with byline and review URL, supporting editorial integrations alongside the bestseller data.

Call /reviews.json?author=Colson+Whitehead and return each review with the published date, byline, and URL.

Agent-Driven Books Lookup via Jentic

An AI reading assistant uses Jentic to discover this NYT Books spec at runtime. The agent searches Jentic by intent, loads the relevant operation schema, and executes the call without manually wiring the api-key or learning the date-format conventions in the path templates.

Search Jentic for 'NYT full bestsellers overview', load the /lists/full-overview.json operation, and execute it.

Key Endpoints

7 endpoints — this nyt books spec is a third-party konfig-sourced bundle that mirrors the nyt books service with one extra endpoint, /lists/full-overview.

METHOD

PATH

DESCRIPTION

GET

/lists.json

Get a Best Sellers list by name

GET

/lists/{date}/{list}.json

Get a Best Sellers list for a specific date

GET

/lists/full-overview.json

Full overview of every active Best Sellers list

GET

/lists/overview.json

Top 5 entries across all active lists

GET

/lists/names.json

List every available Best Sellers list name

GET

/lists/best-sellers/history.json

Full ranking history for a book

GET

/reviews.json

Search NYT critic book reviews

GET

/lists.json

Get a Best Sellers list by name

GET

/lists/{date}/{list}.json

Get a Best Sellers list for a specific date

GET

/lists/full-overview.json

Full overview of every active Best Sellers list

GET

/lists/overview.json

Top 5 entries across all active lists

GET

/lists/names.json

List every available Best Sellers list name

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your NYT api-key is stored once, encrypted, by your own Jentic One instance and injected as the api-key query parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get the full NYT bestsellers overview' or 'look up book ranking history', and Jentic returns the matching Books API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Books API through Jentic.

What authentication does this NYT Books spec use?

Authentication is an API key sent as the api-key query parameter on every endpoint. Provision a key at developer.nytimes.com. Through Jentic the key is held in the vault and injected at request time, so the agent never holds the raw secret.

How does this spec differ from the standard nytimes.com/books_api spec?

This spec is a third-party Konfig-sourced bundle that adds the /lists/full-overview.json endpoint, returning every entry across every active Best Sellers list rather than just the top 5 returned by /lists/overview.json. The other 6 endpoints mirror the standard NYT Books API.

Can I retrieve every Best Sellers list at full depth in one call?

Yes. Call GET /lists/full-overview.json. The response includes every active list with its complete ranked entries, ISBN-13, author, publisher, weeks-on-list, and rank-last-week, removing the need for one request per list.

What are the rate limits for this API?

NYT enforces 500 requests per day and 5 requests per minute per API key, shared across every NYT developer API. The full-overview endpoint returns a large payload, so cache the response for the publication week rather than polling.

How do I look up a book's bestseller history through Jentic?

Search Jentic for 'NYT bestseller history', load the /lists/best-sellers/history.json operation, and execute it with isbn, author, title, or publisher. Jentic returns the parameter schema so the agent picks the correct query parameter without reading docs.

Is this API free to use?

Yes. NYT offers the Books service at no cost on the developer portal for non-commercial use within the published rate limits. Commercial or high-volume use requires direct contact with the NYT licensing team.

Can I limit what my agent is allowed to do with the NYT Books API?

Yes. Because Jentic One is self-hosted, you decide which of the seven read-only operations the agent may call, so you can allow just list overviews and full-overview snapshots while excluding bestseller history or critic reviews. The agent can only reach the endpoints you list, and it never sees the raw NYT api-key because your own instance injects it at request time. Since every operation is GET, the agent can read Best Sellers data but cannot change anything at NYT.