The New York Times Python API Docs | dltHub
Build a The New York Times-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
The New York Times Developer API provides programmatic access to a variety of newsroom content, including articles, book reviews, and popular stories. The REST API base URL is https://api.nytimes.com/svc and all requests require an API key passed as a query string parameter.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading The New York Times data in under 10 minutes.
What data can I load from The New York Times?
Here are some of the endpoints you can load from The New York Times:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| articlesearch | search/v2/articlesearch.json | GET | response.docs | Returns an array of articles based on search criteria. |
| top_stories | topstories/v2/{section}.json | GET | results | Returns top stories by section. |
| most_popular | mostpopular/v2/viewed/{period}.json | GET | results | Returns most popular articles by period. |
| archive | archive/v1/{year}/{month}.json | GET | response.docs | Returns articles for a specific month. |
| newswire | news/v3/content/{source}/{section}.json | GET | results | Returns real-time news articles. |
How do I authenticate with the The New York Times API?
All requests are authenticated by including the registered API key as a query parameter named 'api-key'. No additional headers are required for authentication.
1. Get your credentials
- Navigate to the New York Times Developer Portal (https://developer.nytimes.com/) and sign in or create an account. 2. Once logged in, open the user menu in the top-right corner and select 'Apps'. 3. Click '+ New App' to register a new application. 4. Enter a name and description for your app, and toggle the specific API products you wish to access (e.g., Article Search, Top Stories, Most Popular). 5. Click 'Save'. The generated API key will be displayed on the application details page.
2. Add them to .dlt/secrets.toml
[sources.the_new_york_times_source] api_key = "your_nytimes_api_key_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the The New York Times API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python the_new_york_times_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline the_new_york_times_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset the_new_york_times_data The duckdb destination used duckdb:/the_new_york_times.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads topstories and mostpopular from the The New York Times API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def the_new_york_times_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.nytimes.com/svc", "auth": {"type": "api_key", "api_key": api_key, "name": "api-key", "location": "query"}, }, "resources": [ {"name": "articlesearch", "endpoint": {"path": "svc/search/v2/articlesearch.json", "data_selector": "response.docs"}}, {"name": "top_stories", "endpoint": {"path": "svc/topstories/v2/{section}.json", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="the_new_york_times_pipeline", destination="duckdb", dataset_name="the_new_york_times_data", ) load_info = pipeline.run(the_new_york_times_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("the_new_york_times_pipeline").dataset() sessions_df = data.articlesearch.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM the_new_york_times_data.articlesearch LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("the_new_york_times_pipeline").dataset() data.articlesearch.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load The New York Times data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for The New York Times?
Request dlt skills, commands, AGENT.md files, and AI-native context.