/jiji/categories/articles

POST /api/jiji/categories/articles

Price: 10 credits

List Jiji Press articles in one genre, newest first, with headline, publish time, thumbnail and the url that resolves the story. Newsroom genres serve a rolling window of the latest stories; the syndicated wire genres (prt, prn, bw) page back through several hundred releases. Add day_offset to get a single publication day instead of the rolling window.

How to use it

Browse a Jiji Press genre. category takes a code from jiji/categories/search ('int', 'spo', 'prn'). Without day_offset you get the rolling newest-first feed, which is what the site shows by default; with day_offset you get exactly one publication day (0 today … 3 three days ago) and a different, usually smaller set — the two are not interchangeable. Wire genres keep going for several pages, newsroom genres stop after their window, so a large count simply returns everything there is. Pass web_url (it already carries the genre) or the pair id + category to jiji/articles for the full story; for anything older than the window use jiji/archives.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string required — Genre code to browse, as returned by jiji/categories/search (examples: "int", "spo", "prn"; minLength: 1)
• day_offset integer nullable — Restrict the feed to a single publication day: 0 is today, 1 yesterday and so on up to 3. Leaving it out returns the newest stories across all of those days instead, which is a different and larger set (min: 0; max: 3)
• count integer required — Max number of articles to return (min: 1)

Response

• @type string (default: "JijiArticleCard")
• id string required
• category string nullable
• article_title string required
• web_url string required
• published_at integer nullable
• image string nullable
• has_photo 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 — No such genre 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.