Docs / Data sources / The New York Times

The New York Times

Business software

Built when you ask for it

Sync New York Times articles and archive data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The New York Times connector syncs your editorial content data into analytics-ready tables in your data warehouse. Pull articles, top stories, and book reviews from the NYT Developer APIs, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Articles
  • Top stories
  • Book reviews

How it gets built

  1. Choose The New York Times when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads The New York Times's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against The New York Times itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API key, sent as a query parameter: ?api-key=. Create an app in the NYT Developer portal and enable the specific APIs you need to receive an API key.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a The New York Times connector?
Not as a finished connector yet. Ingest builds it from The New York Times's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can The New York Times data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

The New York Times API documentation: https://developer.nytimes.com/

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request The New York Times