/jiji/articles

POST /api/jiji/articles

Price: 5 credits

Get one Jiji Press article by key or url: headline, lead description, full body text, publish and last-update timestamps, the desk that wrote it, the genres it is filed under, running-story topics, photos with captions, embedded players and related-story links. Members-only pieces are returned in full — the site's paywall is applied in the browser, not on the server.

How to use it

Fetch a single Jiji Press story. article takes the key from a jiji.com url ('2026080600275') or the whole url. Jiji runs several key spaces: its own newsroom keys are 13 digits, Business Wire 14 digits, PR Newswire eight mixed-case characters, PR TIMES two dotted numbers. Newsroom keys resolve on their own; the three wire spaces only resolve together with their genre, so pass category ('prn', 'prt', 'bw') or hand over the full url from jiji/categories/articles, which already carries it. article_type is 'member' for subscriber pieces, whose text is still complete. categories[].id feeds jiji/categories/articles and jiji/archives.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Jiji article key or its full url (examples: "2026080600275", "https://www.jiji.com/jc/article?k=2026080600275&g=spo"; minLength: 1)
• category string nullable — Genre the article is filed under; wire-service stories (PR TIMES, PR Newswire, Business Wire) are only reachable with it (examples: "int", "prn")

Response

• @type string (default: "JijiArticle")
• id string required
• category string nullable
• article_title string required
• headline string nullable
• description string nullable
• text string nullable
• web_url string required
• language string nullable
• section string nullable
• subject string nullable
• published_at integer nullable
• updated_at integer nullable
• author string nullable
• author_id string nullable
• author_url string nullable
• publisher string nullable
• categories array (default: [])
  • @type string (default: "JijiArticleCategory")
  • id string required
  • name string nullable
  • web_url string required
• topics array (default: [])
  • @type string (default: "JijiArticleTopic")
  • name string required
  • web_url string required
• image string nullable
• images array (default: [])
  • @type string (default: "JijiArticleImage")
  • image string required
  • caption string nullable
• embed_urls array (default: [])
• related array (default: [])
  • @type string (default: "JijiRelatedArticle")
  • id string required
  • category string nullable
  • article_title string required
  • web_url string required
• article_type string nullable
• is_members_only boolean required
• has_paywalled_section boolean required
• is_accessible_for_free boolean nullable
• paragraph_count integer 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 article with this key, or the key belongs to a wire genre that was not supplied 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.