/yonhap/articles/reactions

POST /api/yonhap/articles/reactions

Price: 10 credits

Read the reader engagement counters Yonhap News Agency publishes for its wire items, for up to 200 content ids in one call: the four reaction buttons (like, sad, angry, request a follow-up) and the per-network share counters, alongside the headline, dispatch time and the items the desk linked as related.

How to use it

Bulk engagement lookup: pass many content ids at once instead of calling yonhap/articles per id. Only the Korean newsroom's items are counted here - ids from the other seven editions resolve to nothing at all and are skipped, so a request made purely of them comes back as not found. Skipped ids make the result shorter than the request, so match rows back by id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• articles array required — Yonhap content ids, or the article URLs they appear in (examples: ["AKR20260805148500001","https://www.yna.co.kr/view/AKR20260805083152001"]; minItems: 1; maxItems: 200)

Response

• @type string (default: "YonhapArticleEngagement")
• id string required
• language string required
• article_title string required
• web_url string required
• published_at integer nullable
• updated_at integer nullable
• related_articles array (default: [])
  • @type string (default: "YonhapRelatedArticle")
  • id string required
  • article_title string nullable
  • web_url string required
• reactions object nullable
  • @type string (default: "YonhapArticleReactions")
  • like_count integer (default: 0)
  • sad_count integer (default: 0)
  • angry_count integer (default: 0)
  • follow_up_count integer (default: 0)
  • total_count integer (default: 0)
• shares object nullable
  • @type string (default: "YonhapArticleShares")
  • kakao_talk_count integer (default: 0)
  • kakao_story_count integer (default: 0)
  • facebook_count integer (default: 0)
  • facebook_messenger_count integer (default: 0)
  • x_count integer (default: 0)
  • naver_band_count integer (default: 0)
  • naver_blog_count integer (default: 0)
  • url_count integer (default: 0)
  • native_count integer (default: 0)
  • total_count integer (default: 0)

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 — None of the requested content ids resolved 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.