canonical: https://jentic.com/apis/nytimes.com/times-newswire-api

# Nytimes Times Newswire API

The New York Times Times Newswire API is a real-time stream of NYT article URLs and metadata, updated as soon as articles are published on NYTimes.com or sourced from the Associated Press. Three GET endpoints return content from a chosen source (all, nyt, or iht), section, and time-period combination. Each item carries title, byline, abstract, publication date, web URL, geographic facets, organisational facets, and embedded multimedia, supporting near-real-time newsroom monitoring and downstream content distribution.

## For AI agents

Stream the latest NYT and AP article URLs and metadata as soon as they are published, filterable by source and section.

## Scope

Does not provide full article body text, push delivery, or reader engagement metrics - use for chronological streaming of newly-published NYT and AP article metadata only.

## Capabilities

- Stream the latest NYT and AP article URLs as they publish
- Filter the wire to a specific source (NYT or IHT) or all sources
- Restrict the wire to a chosen section such as Politics or Business
- Look back across configurable time-period windows
- Pull article media metadata including image URLs and captions
- Surface geographic and organisational facets attached to each article

## Use cases

### Newsroom Monitor

Build a near-real-time dashboard that surfaces every newly published NYT article in chosen sections. The /content/{source}/{section}.json endpoint returns the latest entries with title, byline, abstract, multimedia, and the canonical URL, so a polling loop every 30 seconds gives a fresh wire view without overrunning rate limits.

Example prompt: Call /content/nyt/all.json every 30 seconds and emit each article URL not seen in the previous response.

### Section-Filtered Content Distribution

Distribute newly published NYT articles to downstream channels filtered by section. The Times Newswire endpoints accept a section path segment so a Politics-only feed can be fed straight into a Slack channel, push notification system, or RSS conversion pipeline.

Example prompt: Call /content/nyt/politics.json every minute and forward new article entries to a Slack channel via webhook.

### Editorial Calendar Backfill

Backfill a wider time window using the /content/{source}/{section}/{time-period}.json endpoint, which supports configurable look-back periods. This lets an editorial system reconstruct the publish timeline for a section over recent hours rather than only the latest snapshot.

Example prompt: Call /content/nyt/business/24.json once per day and ingest the full 24-hour publication list for the Business section.

### Agent-Driven News Monitoring via Jentic

An AI news monitoring agent uses Jentic to pull the latest NYT wire on demand. Jentic returns the matching /content endpoint with its source/section/time-period parameter schema, the agent loads it and executes the call without manually wiring the URL templates.

Example prompt: Search Jentic for 'stream latest NYT articles', load the /content/{source}/{section}.json operation, and execute it with source='nyt' and section='all'.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /content.json | Latest articles across every source and section |
| GET | /content/{source}/{section}.json | Latest articles for a chosen source and section |
| GET | /content/{source}/{section}/{time-period}.json | Articles for a chosen source, section, and time period |

## Key resources

- **All Sources Content** — Latest NYT and IHT articles aggregated by section.
- **Source-Filtered Content** — Articles filtered to a single source (NYT or IHT).
- **Time-Windowed Content** — Articles filtered to a configurable look-back time period.

## Why Jentic

- **Setup:** Wiring the NYT Times Newswire API by hand means registering for an NYT developer key, threading it into the api-key query parameter, and coding your own polling, retry, and rate-limit handling against api.nytimes.com. Through Jentic you install once, import the Times Newswire API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Times Newswire is read-only chronological streaming of newly-published article metadata, so scope it by operation: limit the agent to the content-feed operations it needs, such as the combined feed or a specific source and section, and leave the rest out. You choose which operations it may call, so nothing beyond feed retrieval runs unless you add it.
- **Credential handling:** Your NYT api-key is stored once, encrypted, by your own Jentic One instance and injected into the api-key query parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'stream the latest NYT articles' or 'monitor a NYT section feed', and Jentic returns the matching /content operation with its source, section, and time-period parameters so the agent calls the right endpoint without reading the NYT documentation.

## Related APIs

- **NYT Top Stories API** — Editor-curated section fronts rather than a publish-time-ordered wire feed.
- **NYT Most Popular API** — Engagement-ranked lists that complement Times Newswire's publication-time stream.
- **NYT Community API** — Reader comments on the same article URLs surfaced by Times Newswire.

## FAQ

### What authentication does the NYT Times Newswire API use?

Authentication is an API key passed as the api-key query parameter on every endpoint. Provision a key at developer.nytimes.com. Through Jentic the credential lives in the vault and is injected at execution time, so the agent never sees the raw key.

### How fresh is the Times Newswire data?

The wire updates within seconds of an article's publication on NYTimes.com or arrival from the Associated Press. Polling /content/nyt/all.json every 30 seconds gives near-real-time coverage without exceeding the 5-requests-per-minute cap.

### What are the rate limits for the NYT Times Newswire API?

NYT enforces 500 requests per day and 5 requests per minute per API key, shared across all NYT developer APIs. With the 30-second polling cadence on a single section, a single key can monitor about 2-3 sections simultaneously within budget.

### How do I stream the latest NYT articles through Jentic?

Search Jentic for 'stream latest NYT articles', load the /content/{source}/{section}.json operation, and execute it with source='nyt' and section='all'. Track the URLs returned and emit each new entry on subsequent calls.

### Is the NYT Times Newswire API free to use?

Yes. NYT offers Times Newswire at no cost on the developer portal for non-commercial use within the published rate limits. Commercial redistribution of NYT content requires a separate licensing agreement with the NYT licensing team.

### Does this API include full article body text?

No. The wire returns headline, byline, abstract, URL, multimedia, and tag facets, but not full body text. Use the URL to direct readers to NYTimes.com or pair with the Article Search API for archived content lookups.

### Can I limit what my agent is allowed to do with the Times Newswire API?

Yes. Because you run Jentic One yourself, your own rules decide which Times Newswire operations and credentials the agent can use. Since this API is read-only chronological streaming of newly-published article metadata, you can scope it by operation: allow only the content-feed calls the agent needs, such as the combined /content.json feed or a specific /content/{source}/{section}.json source and section, and leave the rest out. Nothing beyond the feed operations you grant will run, and your stored NYT api-key is injected only for the calls you permit.