/yonhap/articles

POST /api/yonhap/articles

Price: 5 credits

Get a full Yonhap News Agency item by content id (or article URL): headline, sub-headlines, full body text, AI three-line summary, reporters with their profile ids, desk, section and topic taxonomy, keywords, images with wire captions, related items, plus reader reactions and share counters. Works across all eight Yonhap editions (Korean, English, Chinese, Japanese, Arabic, Spanish, French, Vietnamese) and for photo, graphic and video items.

How to use it

Fetch one Yonhap item by its content id (AKR… Korean, AEN… English, ACK… Chinese, AJP… Japanese, AAR… Arabic, ASP… Spanish, AFR… French, AVI… Vietnamese, GYH… graphic, MYH… video, IPT… picture essay, RPR… partner press release, and any P… photo including the wire-agency frames Yonhap redistributes) or by the article URL. Every id the listing and search endpoints return is accepted here. Each edition is an independent newsroom with its own ids and taxonomy, so an English id never resolves on the Korean site. reactions/shares and the three-line summary are only published by the Korean edition.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Yonhap content id, or the full article URL it appears in (examples: "AKR20260805148500001", "https://en.yna.co.kr/view/AEN20260805009851315"; minLength: 1)
• language string nullable — Edition to read the content from. Edition-specific ids (AKR/AEN/ACK/AJP/AAR/ASP/AFR/AVI) already carry their edition, so this is only needed for shared media ids such as photos (one of: "ko", "en", "zh", "ja", "ar", "es", "fr", "vi"; examples: "ko")

Response

• @type string (default: "YonhapArticle")
• id string required
• language string required
• article_title string required
• subtitles array (default: [])
• description string nullable
• text string nullable
• summary array (default: [])
• web_url string required
• published_at integer nullable
• section string nullable
• section_path string nullable
• section_name string nullable
• topics array (default: [])
• keywords array (default: [])
• authors array (default: [])
  • @type string (default: "YonhapArticleAuthor")
  • id string nullable
  • name string required
  • profile_url string nullable
• writer_name string nullable
• desk string nullable
• residence_zone string nullable
• urgency integer nullable
• image string nullable
• images array (default: [])
  • @type string (default: "YonhapArticleImage")
  • id string nullable
  • image string required
  • caption string nullable
  • image_title string nullable
  • is_main boolean (default: false)
• videos array (default: [])
• duration string 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 — Item not found: well-formed id that the requested edition does not publish, or a wire frame that has no standalone page 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.