/mainichi/articles

POST /api/mainichi/articles

Price: 5 credits

Get one Mainichi Shimbun article by id or URL, from either the English edition (The Mainichi) or the Japanese mainichi.jp edition: headline, teaser, body text, byline, publish and update time, photos with captions, section tags, related articles and, for the Japanese edition, whether the story is subscriber-only together with the full and withheld character counts.

How to use it

Fetch one Mainichi article. The id is the article path: ids starting with english/articles/… are English edition stories, ids starting with articles/… are Japanese edition stories; a full URL of either edition works too. Returns one item with edition, article_title, description, text (the body that is publicly readable), published_at and updated_at in unix seconds, image and images, keywords and related_articles. Japanese stories add author_name and author_url, section categories, and the paywall picture: is_premium, char_count_total (the length of the whole story) and char_count_hidden (how much of it stays behind the paywall). English edition stories 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 — Mainichi article id or the full article URL (examples: "english/articles/20260806/p2g/00m/0na/003000c", "articles/20260806/k00/00m/010/001000c"; minLength: 1)

Response

• @type string (default: "MainichiArticle")
• id string required
• edition string required (one of: "en", "jp")
• article_title string required
• description string nullable
• text string nullable
• web_url string nullable
• published_at integer nullable
• updated_at integer nullable
• author_name string nullable
• author_url string nullable
• paper string nullable
• label string nullable
• badges array (default: [])
• image string nullable
• images array (default: [])
  • @type string (default: "MainichiArticleImage")
  • image string required
  • caption string nullable
• categories array (default: [])
  • @type string (default: "MainichiArticleCategory")
  • id string required
  • name string required
  • web_url string nullable
• keywords array (default: [])
• related_articles array (default: [])
  • @type string (default: "MainichiRelatedArticle")
  • id string required
  • article_title string required
  • web_url string nullable
• is_premium boolean (default: false)
• char_count_total integer nullable
• char_count_hidden 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 a Mainichi 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.