/yonhap/issues/search

POST /api/yonhap/issues/search

Price: 10 credits

Browse the catalog of Yonhap News Agency issues - the curated dossiers the newsroom keeps on running stories - optionally narrowed to one desk. Each entry carries the issue id, headline, cover image, how many articles, wire photos, videos and graphics are filed under it, and the three newest headlines.

How to use it

Discovery entry point for Yonhap issues: returns issue ids for yonhap/issues and yonhap/issues/articles. Issues are ordered by the most recent dispatch filed under them, so the head of the list is what the newsroom is actively covering. Korean newsroom only.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category string — Desk the issues belong to (default: "all"; one of: "all", "politics", "nk", "economy", "it", "society", "international", "sports-entertainment")
• count integer required — Number of issues to return (min: 1; max: 360)

Response

• @type string (default: "YonhapIssueSummary")
• id string required
• issue_title string required
• web_url string required
• image string nullable
• article_count integer (default: 0)
• photo_count integer (default: 0)
• video_count integer (default: 0)
• graphic_count integer (default: 0)
• latest_articles array (default: [])
  • @type string (default: "YonhapIssueArticleLink")
  • id string required
  • article_title string required
  • web_url string 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 — The entity was not found, or a precondition failed 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.