/jiji/categories/search

POST /api/jiji/categories/search

Price: 5 credits

List the genres Jiji Press browses by — desks such as int, pol, eco, soc and spo, running stories such as ukr or ieq, and the syndicated wires prt, prn and bw — with the Japanese label the site shows for each. Genres that keep a month-by-month archive also carry the list of months available, which jiji/archives accepts directly.

How to use it

Discover Jiji genre codes instead of guessing them: every id here goes straight into jiji/categories/articles. has_archive marks the handful of genres that also keep a monthly archive, and archive_months lists exactly which YYYY-MM values jiji/archives will serve for them (about a year back). This is the site's own navigation, so a few thematic genres that only appear on article tag lists are missing from it — any code you get back in the categories field of jiji/articles is equally valid input.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of categories to return (min: 1)

Response

• @type string (default: "JijiCategory")
• id string required
• name string nullable
• web_url string required
• archive_months array (default: [])
• has_archive boolean required

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.