/kommersant/articles

POST /api/kommersant/articles

Price: 5 credits

Get a full Kommersant article by URL or numeric id: title, subtitle, description, full text, publish and update dates, keywords, authors, mentioned topics (people, organizations), publication name and lead image.

How to use it

Get a single Kommersant article by its URL or bare numeric id. Returns one item with title, subtitle, description, text (full body), published_at/updated_at, keywords, authors (with profile links), topics (people and organizations the article is about, with Wikidata links), publication name and image.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Kommersant article URL or numeric article id (examples: "https://www.kommersant.ru/doc/8511593", "8511593"; minLength: 1)

Response

• @type string (default: "KommersantArticle")
• id integer required
• subtitle string nullable
• description string nullable
• text string nullable
• published_at string nullable
• updated_at string nullable
• keywords array (default: [])
• authors array (default: [])
  • @type string (default: "KommersantArticleAuthor")
  • id integer nullable
  • name string required
  • profile_url string nullable
• topics array (default: [])
  • @type string (default: "KommersantArticleTopic")
  • name string required
  • type string nullable
  • wikidata_url string nullable
• publication string nullable
• image string nullable
• web_url string nullable

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 — Article not found (well-formed but nonexistent id or URL) 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.