/yonhap/photos

POST /api/yonhap/photos

Price: 5 credits

Get one Yonhap News Agency wire photo by its photo id or URL: the wire caption, every published size of the image, the photographer with their reporter profile id and desk, the filing section and topics, hashtags, dispatch time and the reader reaction and share counters.

How to use it

Photo ids start with P: PYH is Yonhap's own picture desk, PRU/PAP/PEP/PUP/PAF/PXI/PGT are the wire agencies Yonhap redistributes. Picture essays (IPT) and graphics (GYH) are different item types and are read with yonhap/articles. Find photo ids with yonhap/categories/photos, yonhap/issues/articles or the most_viewed_photo feed of yonhap/articles/rankings.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• photo string required — Yonhap photo id, or the full photo URL it appears in (examples: "PYH20260805189100013", "https://www.yna.co.kr/view/PYH20260805185600013"; minLength: 1)

Response

• @type string (default: "YonhapPhoto")
• id string required
• photo_title string required
• caption string nullable
• web_url string required
• image string nullable
• images array (default: [])
• photographer string nullable
• photographer_id string nullable
• photographer_url string nullable
• photographer_email string nullable
• desk string nullable
• section string nullable
• published_at integer nullable
• updated_at integer nullable
• topics array (default: [])
• keywords array (default: [])
• urgency integer nullable
• 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 — Photo not found: well-formed photo id that has no photo page (some agency frames are only published inside articles) 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.