Nytimes APIs

12 APIs33 Endpoints2 Categories

API Catalog(3 of 12)

Geographic API

The New York Times Geographic API extends the NYT Semantic API with a linked-data layer that resolves location concepts in the NYT controlled vocabulary against external geographic data sources. A single /query.json endpoint accepts a place name or NYT geo concept identifier and returns enriched location records with coordinates, geo facets, and references to the NYT articles tagged with that location. It is designed for agents that need to disambiguate place names mentioned in NYT coverage and link them to consistent geographic identifiers.

1 endpoints

Semantic API

The New York Times Semantic API exposes the NYT controlled vocabulary of people, places, organizations, descriptors, titles of works, and other named entities used to tag NYT articles. Two endpoints support the workflow: /search.json returns concepts matching a query string with optional concept-type filtering, and /name/{concept-type}/{specific-concept}.json returns the linked-data record for a single concept including article references, related concepts, and external resource links. The API is designed for entity linking, knowledge-graph enrichment, and disambiguating named entities mentioned in editorial content.

2 endpoints

TimesTags API

The New York Times TimesTags API is an autocomplete service over the NYT controlled vocabulary used to tag NYT articles. A single /timestags endpoint accepts a partial query string and returns ranked tag suggestions across persons, organizations, locations, descriptors, titles of works, and other entity types. Each suggestion includes the canonical tag string with a leading classifier (e.g. 'Per:', 'Org:', 'Geo:'), letting an autocomplete UI label suggestions by entity type. The API is the recommended front door for type-ahead lookups before deeper linked-data calls into the Semantic and Geographic APIs.

1 endpoints

Connect Your Agent

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.