/naver/cafe/posts/search

POST /api/naver/cafe/posts/search

Price: 5 credits

Search Naver Cafe posts across all public cafes by words, by relevance or newest: post and cafe ids, title, snippet, cafe name and alias, images, price and sale status of trade posts, date

How to use it

Pass a row id (cafeId/articleId) to naver/cafe/posts for the full post or naver/cafe/posts/comments for its comments. Posts on member-only boards are not readable there and answer 412, and a search row does not show which ones; naver/cafe/cafes/posts marks board rows with is_public. For second-hand listings with price and delivery filters use naver/cafe/trades/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Words to search for (examples: "캠핑", "아이폰 중고"; minLength: 1)
• count integer required — Max number of results (examples: 50; min: 1; max: 1000)
• sort string — Order of the results (default: "relevance"; one of: "relevance", "newest")

Response

• @type string (default: "NaverCafePostSearchResult")
• id string required
• cafe_id string required
• article_id string required
• url string required
• snippet string nullable
• cafe_name string nullable
• cafe_alias string nullable
• cafe_image string nullable
• menu_id string nullable
• image string nullable
• images array (default: [])
• image_count integer nullable
• is_power_cafe boolean nullable
• is_town_cafe boolean nullable
• price integer nullable
• sale_status string nullable
• product_condition string nullable
• delivery_types array (default: [])
• created_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 — The entity was not found, or a precondition failed 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.