/jiji/archives

POST /api/jiji/archives

Price: 5 credits

Read a whole calendar month of Jiji Press articles in one genre — every story the desk filed that month, newest first, with headline, publish time and the url that resolves it. The site keeps roughly the last twelve months and only for its main desks; jiji/categories/search reports which genres and which months are available.

How to use it

Go back further than the rolling feed of jiji/categories/articles. category must be one of the genres whose has_archive is true in jiji/categories/search, and month must be one of the values that endpoint lists in archive_months — anything outside that window is not served. A single month can hold several hundred stories and arrives in one page, so set count generously. Pass web_url or id + category on to jiji/articles for the text.

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 with a monthly archive, as marked by has_archive in jiji/categories/search (examples: "int", "soc"; minLength: 1)
• month string required — Calendar month to read, as YYYY-MM (examples: "2026-07"; pattern: ^\d{4}-\d{2}$)
• 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 — This genre keeps no archive, or the requested month is outside the window the site serves 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.