Automate New York Times Semantic

What New York Times Semantic is

The Semantic API complements the Articles API. With the Semantic API, you get access to the long list of people, places, organizations and other locations, entities and descriptors that make up the controlled vocabulary used as metadata by The New York Times (sometimes referred to as Times Tags and used for Times Topics pages). The Semantic API uses concepts which are, by definition, terms in The

API host: api.nytimes.com

What HumDay can read from New York Times Semantic

These are the operations a schedule or a trigger can watch.

• GETRead search json/search.json
• GETRead specific concept json/name/{concept-type}/{specific-concept}.json

How automating New York Times Semantic works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live New York Times Semantic account.
4. Grant access, then go live. You approve the specific New York Times Semantic operations it may use — and only those.

Automate New York Times Semantic with these

• New York Times Archive1 operations
• New York Times Article Search1 operations
• New York Times Books6 operations
• New York Times Community4 operations
• New York Times Geographic1 operations
• New York Times Most Popular3 operations
• New York Times Movie Reviews3 operations
• New York Times Times Newswire3 operations
• New York Times TimesTags1 operations
• New York Times Top Stories1 operations
• Google Compute Engine694 operations
• Jellyfin379 operations

Categories

• Media
• Open data

Questions about New York Times Semantic automation

Can HumDay connect to New York Times Semantic?

Yes. HumDay reads New York Times Semantic's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 2 operations are documented.

Do I need to write code to automate New York Times Semantic?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your New York Times Semantic account.

What can HumDay do in New York Times Semantic?

0 of the 2 documented operations change something in New York Times Semantic, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my New York Times Semantic account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to New York Times Semantic is held behind that approval.

Where this came from

The operations above are read from a published API description for New York Times Semantic at raw.githubusercontent.com/nytimes/public_api_specs/master/semantic_api/semantic_api.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.