# /yonhap/articles/search

`POST /api/yonhap/articles/search`

Price: 10 credits

Full-text search over Yonhap News Agency articles in any of the eight editions. Filters: match the keyword against the whole article, headline or body; restrict to one desk (politics, economy, society, culture, North Korea, international, sports, entertainment); bound the dispatch date; restrict to a reporter byline; order by recency or relevance. Returns content id, headline, matched excerpt, thumbnail, dispatch time, keywords and byline.

## How to use it

Search Yonhap articles by keyword. Each edition indexes only its own articles, so search the edition whose language the keyword is written in. The index covers roughly the last year of dispatches: a date_to older than that is rejected as an unsearchable window, and a date_from older than that is clamped to the start of the index. Ids returned here work with yonhap/articles. writer_id is the desk writer code and is a different identifier space from the reporter ids used by yonhap/authors - resolve a byline through yonhap/articles (authors[].id) or yonhap/authors/search instead.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keyword` (string, required) — Search keyword (examples: "삼성전자"; minLength: 1)
- `language` (string) — Yonhap edition to search in; each edition indexes only its own articles (default: "ko"; one of: "ko", "en", "zh", "ja", "ar", "es", "fr", "vi")
- `scope` (string) — Match the keyword against the whole article, the headline or the body (default: "all"; one of: "all", "title", "body")
- `category` (string) — Restrict results to one desk (default: "all"; one of: "all", "01", "02", "05", "07", "10", "11", "12", "0712")
- `date_from` (string, nullable) — Earliest dispatch date, YYYY-MM-DD (examples: "2026-01-01")
- `date_to` (string, nullable) — Latest dispatch date, YYYY-MM-DD (examples: "2026-01-31")
- `reporter_name` (string, nullable) — Restrict results to articles bylined by this reporter (examples: "박형빈")
- `sort` (string) — Result ordering (default: "date"; one of: "date", "weight")
- `count` (integer, required) — Number of articles to return (min: 1; max: 3000)

## Response

### 200 — Successful Response

- `@type` (string) (default: "YonhapSearchArticle")
- `id` (string, required)
- `language` (string, required)
- `article_title` (string, required)
- `description` (string, nullable)
- `web_url` (string, required)
- `image` (string, nullable)
- `published_at` (integer, nullable)
- `keywords` (array) (default: [])
- `section_codes` (array) (default: [])
- `writer_id` (string, nullable)
- `writer_name` (string, nullable)
- `urgency` (integer, nullable)

## Errors

### 422 — Validation Error

The requested date window ends before the searchable index begins

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.