/yonhap/authors

POST /api/yonhap/authors

Price: 1 credit

Get a Yonhap News Agency reporter profile by id: name, desk bio, work email, portrait, subscriber count with gender and age-range breakdown, and the reporter's most recent dispatch.

How to use it

Fetch one Yonhap reporter by the id that appears in their profile URL and in the authors[] block of yonhap/articles. Use yonhap/authors/search to look reporters up by name, and yonhap/authors/articles for their dispatch history.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• author string required — Yonhap reporter id, or the reporter profile URL it appears in (examples: "39343139393937", "https://www.yna.co.kr/reporter/list?id=39343139393937"; minLength: 1)

Response

• @type string (default: "YonhapAuthor")
• id string required
• name string required
• language string nullable
• email string nullable
• description string nullable
• image string nullable
• profile_url string required
• is_active boolean (default: false)
• subscriber_count integer (default: 0)
• subscriber_genders array (default: [])
  • @type string (default: "YonhapAuthorSubscriberSegment")
  • segment string required
  • subscriber_count integer required
• subscriber_age_ranges array (default: [])
  • @type string (default: "YonhapAuthorSubscriberSegment")
  • segment string required
  • subscriber_count integer required
• statistics_date string nullable
• latest_article_id string nullable
• latest_article_title string nullable
• latest_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 — Reporter not found: well-formed id with no profile behind it 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.