POST /api/mainichi/articles/search
Price: 5 credits
Search Mainichi Shimbun articles by keyword in either the English or the Japanese edition, with filters for the publication window, the result ordering and whether every keyword word must match. Returns headline, url, teaser, publish time, thumbnail, story length and, in the Japanese edition, whether the story is subscriber-only.
Search The Mainichi. edition picks which newsroom to search — en for the English edition, jp for the Japanese one; the two carry different stories, and a Japanese keyword only finds anything with edition=jp. sort switches between newest, oldest and relevance; date_range narrows to the last day, week, month or year; match=any_word broadens a multi-word keyword. Every item carries an id that mainichi/articles accepts. A keyword nobody wrote about returns an empty list.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string required — Search keyword (examples: "nuclear", "原発"; minLength: 1; maxLength: 200)count integer required — Max number of results (min: 1)edition string — Search the English edition or the Japanese edition (default: "en"; one of: "en", "jp")date_range string — Restrict results to a recent time window (default: "any_time"; one of: "any_time", "past_24_hours", "past_week", "past_month", "past_year")sort string — Result ordering (default: "newest"; one of: "newest", "oldest", "relevance")match string — Require every keyword word to match, or any one of them (default: "all_words"; one of: "all_words", "any_word")@type string (default: "MainichiArticleCard")id string requirededition string required (one of: "en", "jp")article_title string requiredweb_url string nullableexcerpt string nullablepublished_at integer nullableimage string nullablelabel string nullablebadges array (default: [])char_count integer nullableis_premium boolean (default: false)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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.