/asahi/categories/articles

POST /api/asahi/categories/articles

Price: 10 credits

List Asahi Shimbun articles in one section, newest first. Sections come from both editions: English Asia & Japan Watch sections and Japanese asahi.com sections. Returns headline, url, publish time, teaser, photo and, for the Japanese edition, whether the article is subscriber-only.

How to use it

List one Asahi Shimbun section newest first. Pick a category value: ajw/… values are English Asia & Japan Watch sections, jp/… values are Japanese asahi.com sections. Every item carries an id that asahi/articles accepts. Japanese sections also return excerpt, image_caption, label, is_premium, has_video and groups (the prefectures and running series a story is filed under); English sections return headline, url, published_at and image. Sections that hold no articles simply return an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Section to list. Values prefixed with ajw/ are English Asia & Japan Watch sections, values prefixed with jp/ are Japanese asahi.com sections (one of: "ajw/new", "ajw/national_report", "ajw/politics", "ajw/business", "ajw/asia_world/china", "ajw/asia_world/korean_peninsula", "ajw/asia_world/around_asia", "ajw/asia_world/world", "ajw/sci_tech", "ajw/culture/style", "ajw/culture/food", "ajw/culture/movies", "ajw/culture/manga_anime", "ajw/culture/people", "ajw/travel", "ajw/sports", "ajw/opinion/editorial", "ajw/opinion/vox", "ajw/opinion/views", "jp/society", "jp/society/incident", "jp/society/topics", "jp/society/disaster", "jp/society/investigation", "jp/society/obituaries", "jp/society/gender", "jp/society/peace", "jp/society/human_rights", "jp/politics", "jp/politics/economic_policy", "jp/politics/government", "jp/politics/diplomacy", "jp/politics/local", "jp/business", "jp/business/industry", "jp/business/global", "jp/business/work", "jp/international", "jp/international/asia", "jp/international/north_america", "jp/international/latin_america", "jp/international/europe", "jp/international/middle_east", "jp/international/africa", "jp/international/other", "jp/sports", "jp/opinion", "jp/opinion/interview", "jp/opinion/column", "jp/tech_science", "jp/tech_science/science", "jp/tech_science/digital", "jp/tech_science/environment", "jp/tech_science/energy", "jp/tech_science/nuclear_power", "jp/tech_science/energy_policy", "jp/tech_science/climate_change", "jp/culture", "jp/culture/music", "jp/culture/art", "jp/lifestyle", "jp/lifestyle/travel", "jp/lifestyle/food", "jp/lifestyle/housing", "jp/lifestyle/money", "jp/education", "jp/education/parenting", "jp/education/school", "jp/education/university", "jp/education/policy", "jp/regional", "jp/great_east_japan_earthquake"; examples: "ajw/politics", "jp/society")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "AsahiCategoryArticle")
• id string required
• edition string required (one of: "ajw", "jp")
• article_title string required
• web_url string nullable
• published_at integer nullable
• excerpt string nullable
• image string nullable
• image_caption string nullable
• label string nullable
• is_premium boolean (default: false)
• has_video boolean (default: false)
• groups array (default: [])
  • @type string (default: "AsahiCategoryGroup")
  • group_type string nullable
  • name string required
  • 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.