New York Times
The New York Times Developer APIs provide programmatic access to Times content, including article search, top stories by section, most-popular articles, Best Sellers book lists and reviews, and the Times Newswire real-time feed. Nexla connects to these APIs to ingest news and book data for search, analysis, and enrichment. Authentication uses an API key issued through the NYT Developer Portal.
Power end-to-end data operations for your New York Times API with Nexla. Our bi-directional New York Times connector is purpose-built for New York Times, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to New York Times or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your New York Times workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a New York Times credential, you need an API key from the NYT Developer Portal. The New York Times APIs authenticate each request with an API key that is sent as the api-key URL query parameter.
To obtain your API key, follow these steps:
-
Go to the NYT Developer Portal and sign in, or create a free developer account if you do not already have one.
-
Open the account menu in the top-right corner and select Apps.
-
Click + New App (or Create App) to register a new application. Enter a name and a short description for the app.
-
Enable the specific APIs your integration needs by toggling them on for the app — for example, Article Search API, Top Stories API, Most Popular API, Books API, and Times Newswire API.
-
Click Save to create the app. The app's detail page displays the generated API Key.
-
Copy the API Key and store it securely. You will enter this value when creating your Nexla credential.
Each API has its own rate limits, and access to individual APIs is controlled by which APIs you enabled for your app. If you receive an authorization error for a specific endpoint, confirm that the corresponding API is enabled for the app whose key you are using. For details on each API and its parameters, see the NYT Developer Portal API reference.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key Value | Yes | Yes | An encoded string value used as a secret token to authenticate API requests |
Create a credential in Nexla
-
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter your New York Times API key in the API Key Value field. This is the key generated for your app in the NYT Developer Portal that you obtained in Prerequisites. Nexla sends this value as the
api-keyURL query parameter on every request, and it should be kept confidential.Access to each New York Times API is controlled by the APIs you enabled for your app. If a request returns an authorization error, confirm that the corresponding API is enabled for the app whose key you are using.
For detailed information about the available APIs, their parameters, and rate limits, see the NYT Developer Portal.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the New York Times connector tile, then select the credential that will be used to connect to the New York Times APIs, and click Next; or, create a new New York Times credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common New York Times endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
New York Times data sources can also be manually configured to ingest data from any valid New York Times API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new New York Times data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.