/naver/news/articles/comments

POST /api/naver/news/articles/comments

Price: 5 credits

Get comments on a Naver news article. Returns text, author, like/dislike counts, timestamps.

How to use it

Get top-level comments on a Naver news article by its URL or 'officeId/articleId' pair. Order by best, newest, oldest, or reply count. Returns each comment's text, masked author name and profile image, like and dislike counts, reply count, best/blind/deleted flags, and creation and modification 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)
• count integer required — Max number of results (examples: 20; min: 1)
• sort string — Result ordering (default: "best"; one of: "best", "new", "old", "reply")

Response

• @type string (default: "NaverComment")
• id string required
• parent_id string nullable
• reply_count integer (default: 0)
• text string nullable
• user_id string nullable
• user_name string nullable
• user_image string nullable
• like_count integer (default: 0)
• dislike_count integer (default: 0)
• is_best boolean (default: false)
• is_deleted boolean (default: false)
• is_blind boolean (default: false)
• hidden_by_cleanbot boolean (default: false)
• created_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.