/naver/cafe/cafes/posts

POST /api/naver/cafe/cafes/posts

Price: 5 credits

List the newest posts of one Naver Cafe, all boards or one board: post id, title, snippet, image, board, author nickname and level, public flag, view, comment and like counts, media flags and time

How to use it

Rows with is_public false are member-only and naver/cafe/posts answers 412 for them. Board ids come from the menu_id of earlier rows.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• cafe string required — Naver Cafe id, alias or URL (examples: "14358379", "joonggonara", "https://cafe.naver.com/campingfirst"; minLength: 1)
• count integer required — Max number of posts (examples: 50; min: 1; max: 5000)
• menu_id string nullable — Board (menu) id inside the cafe; all boards when omitted (examples: "13")

Response

• @type string (default: "NaverCafeBoardPost")
• id string required
• cafe_id string required
• article_id string required
• url string required
• snippet string nullable
• image string nullable
• menu_id string nullable
• menu_name string nullable
• head string nullable
• author string nullable
• author_level string nullable
• is_public boolean nullable
• read_level integer nullable
• view_count integer nullable
• comment_count integer nullable
• like_count integer nullable
• reply_count integer nullable
• has_image boolean nullable
• has_video boolean nullable
• has_file boolean nullable
• has_poll boolean nullable
• is_trade boolean nullable
• is_popular boolean nullable
• created_at integer nullable

Errors

• 422 — cafe is not a Naver Cafe id, alias or URL 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 Naver Cafe under that id or alias 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.