/naver/news/articles

POST /api/naver/news/articles

Price: 10 credits

Get a Naver news article by office and article ID. Includes title, body, journalist, press, dates.

How to use it

Get a single Naver news article by its URL or 'officeId/articleId' pair. Returns the headline, body text, lead summary, description, press outlet name and category, journalist, section, cover and inline images, the original press URL, and published/modified timestamps.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Naver news article URL or 'officeId/articleId' pair (examples: "https://n.news.naver.com/mnews/article/666/0000114022", "666/0000114022"; minLength: 1)

Response

• @type string (default: "NaverArticle")
• oid string required
• aid string required
• article_url string required
• gdid string nullable
• article_title string nullable
• summary string nullable
• text string nullable
• description string nullable
• press_name string nullable
• press_url string nullable
• press_category string nullable
• journalist string nullable
• journalist_id string nullable
• section_id string nullable
• section_name string nullable
• image string nullable
• images array (default: [])
• original_url string nullable
• published_at integer nullable
• modified_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 — Article not found for the given ID. 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.