/nhk/topics/search

POST /api/nhk/topics/search

Price: 5 credits

List the curated NHK news topic and special-site feeds: the topic tags, in-depth strands and special coverage sites that NHK publishes under each news genre, each with its list id and web url.

How to use it

Catalogue of the feeds NHK curates by hand. Each item carries id (feed the value to nhk/articles/search via the playlist parameter, or to nhk/playlists), topic_id when the feed is a plain topic tag (usable as the topic parameter of nhk/articles/search), genre_id, genre_name and section (which shelf of the genre menu the feed sits on). The genre parameter keeps only the feeds of one genre.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• genre string nullable — Keep only the feeds published under this genre (one of: "society", "politics", "business", "disaster", "international", "scienceculture", "sports", "life"; examples: "sports")
• count integer required — Max number of feeds to return (min: 1; max: 500)

Response

• @type string (default: "NhkTopicFeed")
• id string required
• name string required
• topic_id string nullable
• genre_id string nullable
• genre_name string nullable
• section string nullable
• web_url string nullable

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.