/yomiuri/articles

POST /api/yomiuri/articles

Price: 5 credits

Get one article from The Japan News (the English edition of The Yomiuri Shimbun) by id or URL: headline, teaser, full body text, byline and news-service credit, section path, publish and update time, photos with captions and credits, hashtags and keywords.

How to use it

Fetch one Japan News article by its id (20260806-342028), by the bare numeric part of that id, or by pasting the full article URL. Returns one item with article_title, description, text (the full body), published_at and updated_at in unix seconds, byline (which names the news service for wire stories), section and parent_section with their urls, image and images, tags (ids usable in yomiuri/tags/articles) and keywords. is_subscriber_tier marks stories the newsroom files under its paid tier; text still holds the whole story either way.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Japan News article id or the full article URL (examples: "20260806-342028", "https://japannews.yomiuri.co.jp/society/general-news/20260806-342028/"; minLength: 1)

Response

• @type string (default: "YomiuriArticle")
• id string required
• article_title string required
• description string nullable
• text string nullable
• web_url string nullable
• published_at integer nullable
• updated_at integer nullable
• byline string nullable
• section string nullable
• section_url string nullable
• parent_section string nullable
• parent_section_url string nullable
• author_name string nullable
• author_url string nullable
• author_image string nullable
• image string nullable
• images array (default: [])
  • @type string (default: "YomiuriArticleImage")
  • image string required
  • caption string nullable
  • credit string nullable
• tags array (default: [])
  • @type string (default: "YomiuriArticleTag")
  • id string required
  • name string required
  • web_url string nullable
• keywords array (default: [])
• is_subscriber_tier boolean (default: false)

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 — Article not found — the id or URL does not resolve to a Japan News article 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.