/yonhap/issues/articles

POST /api/yonhap/issues/articles

Price: 20 credits

List what Yonhap News Agency has filed under one issue - the newsroom's curated dossier on a running story - newest first: content id, headline, lead paragraph, thumbnail and dispatch time. The same issue can be read as articles, wire photos, videos or graphics.

How to use it

Full stream of one Yonhap issue (IIS…), newest first. Ids returned here work with yonhap/articles, and photo ids also with yonhap/photos. An issue can hold thousands of items but only the newest 360 per content type are reachable. yonhap/issues reports how many items of each kind exist.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• issue string required — Yonhap issue id, or the full issue URL it appears in (examples: "IIS20260223000001365", "https://www.yna.co.kr/view/IIS20260714000004365"; minLength: 1)
• content_type string — Kind of newsroom output to list from the issue (default: "articles"; one of: "articles", "photos", "videos", "graphics")
• count integer required — Number of items to return (min: 1; max: 360)

Response

• @type string (default: "YonhapIssueItem")
• id string required
• language string required
• article_title string required
• description string nullable
• web_url string required
• image string nullable
• published_at integer 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 — Issue not found: well-formed issue id that Yonhap does not publish 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.