/naver/cafe/posts/comments

POST /api/naver/cafe/posts/comments

Price: 10 credits

List the comments and replies of one public Naver Cafe post, oldest or newest first: text, image, sticker, author nickname and level, post-author flag, reply target and last edit time

How to use it

Pass a post id (cafeId/articleId) or URL from naver/cafe/posts/search or naver/cafe/cafes/posts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• post string required — Naver Cafe post URL or cafeId/articleId pair (examples: "https://cafe.naver.com/f-e/cafes/14358379/articles/3404863", "14358379/3404863"; minLength: 1)
• count integer required — Max number of comments (examples: 100; min: 1; max: 2000)
• order string — Comment order (default: "oldest"; one of: "oldest", "newest")

Response

• @type string (default: "NaverCafeComment")
• id string required
• post_id string required
• parent_id string nullable
• is_reply boolean nullable
• url string required
• text string nullable
• image string nullable
• sticker string nullable
• author string nullable
• author_level string nullable
• author_image string nullable
• is_post_author boolean nullable
• reply_to string nullable
• is_deleted boolean nullable
• is_best boolean nullable
• updated_at integer nullable

Errors

• 422 — post is not a Naver Cafe post URL or cafeId/articleId pair 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 — No such Naver Cafe post, it was deleted, or it is visible to cafe members only 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.