/asahi/articles

POST /api/asahi/articles

Price: 5 credits

Get one Asahi Shimbun article by id or URL, from either the English Asia & Japan Watch edition or the Japanese asahi.com edition: headline, teaser, body text, byline, the full chain of sections the story is filed under, publish and update time, photos with captions, topic tags, related articles and, for the Japanese edition, the reporters who wrote it and whether the article is subscriber-only with how many characters stay behind the paywall.

How to use it

Fetch one Asahi Shimbun article. The id decides the edition: an all-digit id such as 16787244 is an English Asia & Japan Watch article, an alphanumeric id such as ASV852W2ZV85UTFL01YM is a Japanese asahi.com article. A full article URL of either edition is accepted too. Returns one item with edition, article_title, description, text (the body that is publicly readable), published_at and updated_at in unix seconds, byline, image and images, keywords, topics and related_articles. sections lists every desk the story is filed under, from the broad one down to the narrow one, each with its own url; section repeats the first of them. Japanese articles also carry authors, one entry per reporter with their desk, beat and profile. Japanese articles can be subscriber-only: is_premium is then true, text holds only the free opening and remaining_char_count says how many characters are withheld. English edition articles are published in full.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Asahi Shimbun article id or the full article URL (examples: "16787244", "ASV852W2ZV85UTFL01YM"; minLength: 1)

Response

• @type string (default: "AsahiArticle")
• id string required
• edition string required (one of: "ajw", "jp")
• 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
• authors array (default: [])
  • @type string (default: "AsahiArticleAuthor")
  • id string nullable
  • name string required
  • department string nullable
  • role string nullable
  • specialty string nullable
  • description string nullable
  • image string nullable
  • web_url string nullable
  • can_send_fan_letter boolean (default: false)
• section string nullable
• section_url string nullable
• sections array (default: [])
  • @type string (default: "AsahiArticleSection")
  • name string required
  • web_url string nullable
• label string nullable
• image string nullable
• images array (default: [])
  • @type string (default: "AsahiArticleImage")
  • image string required
  • caption string nullable
  • photo_id string nullable
• keywords array (default: [])
• is_premium boolean (default: false)
• remaining_char_count integer nullable
• topics array (default: [])
  • @type string (default: "AsahiArticleTopic")
  • id string nullable
  • name string required
  • web_url string nullable
• related_articles array (default: [])
  • @type string (default: "AsahiRelatedArticle")
  • id string required
  • article_title string required
  • web_url string nullable
  • published_at integer 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 — Article not found — the id or URL does not resolve to an Asahi Shimbun 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.