/nhk/articles/search

POST /api/nhk/articles/search

Price: 20 credits

List NHK news articles from one feed: the nationwide latest stream, a nationwide genre stream, a regional bureau stream, a topic stream, a single day, or any NHK list id. Returns article cards with headline, teaser, last-update time, genre, region, topic tags, images and on-demand video links.

How to use it

Pick at most one feed selector: genre for a nationwide section, area for a regional bureau, topic for a topic id taken from topics[].id of an article or from nhk/topics/search, or playlist for any other NHK list id (editorial and special-site feeds). With no selector the nationwide latest stream is read. date (YYYYMMDD) narrows genre, area or the latest stream to a single day and reaches back to 2019; it cannot be combined with topic or playlist. A day bucket, and the updated_at a card carries, both follow the last-update moment, so a story updated the next day sits in that day's bucket; the first-publication moment lives on nhk/articles as published_at. Cards carry id and web_url that nhk/articles accepts, and playlist_id that nhk/playlists accepts. The article body is not part of a card — call nhk/articles for the full text.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• genre string nullable — Nationwide genre feed to read (one of: "society", "politics", "business", "disaster", "international", "scienceculture", "sports", "life"; examples: "society")
• area string nullable — Regional bureau feed to read (one of: "010", "020", "030", "040", "050", "060", "070", "080", "090", "100", "110", "120", "130", "140", "150", "160", "170", "180", "190", "200", "210", "220", "230", "240", "250", "260", "270", "280", "290", "300", "310", "320", "330", "340", "350", "360", "370", "380", "390", "400", "401", "410", "420", "430", "440", "450", "460", "470"; examples: "130")
• topic string nullable — Topic id to read, as returned in topics[].id of an article (examples: "0000009")
• playlist string nullable — Raw NHK list id or list URL to read, for feeds that the other selectors do not cover (examples: "editorial-nwa-0000000020")
• date string nullable — Single publication day to read, as YYYYMMDD (examples: "20260806")
• count integer required — Max number of articles to return (min: 1; max: 2000)

Response

• @type string (default: "NhkArticleCard")
• id string required
• article_title string required
• description string nullable
• updated_at integer nullable
• web_url string nullable
• genres array (default: [])
• genre_id string nullable
• genre_slug string nullable
• area_id string nullable
• playlist_id string nullable
• playlist_name string nullable
• topics array (default: [])
  • @type string (default: "NhkTopic")
  • id string required
  • name string required
  • is_displayed boolean (default: false)
• image string nullable
• thumbnail string nullable
• videos array (default: [])
  • @type string (default: "NhkVideo")
  • video_title string nullable
  • description string nullable
  • duration number nullable
  • embed_url string nullable
  • image string nullable
  • stream_type string nullable
  • environment_id string nullable
  • streams array (default: [])
    • @type string (default: "NhkVideoStream")
    • name string nullable
    • stream_url string required
    • formats array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.