/naver/cafe/cafes/search

POST /api/naver/cafe/cafes/search

Price: 5 credits

Search Naver Cafe communities by name and description, by relevance, ranking, members, new posts or total posts: cafe id and alias, name, description, manager, topic and region, keywords, member and post counts, rank

How to use it

Pass a row id or alias to naver/cafe/cafes for the cafe profile or naver/cafe/cafes/posts for its posts.

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 in cafe names and descriptions (examples: "캠핑"; minLength: 1)
• count integer required — Max number of results (examples: 50; min: 1; max: 2000)
• sort string — Order of the results (default: "relevance"; one of: "relevance", "ranking", "members", "new_posts", "total_posts")

Response

• @type string (default: "NaverCafeSearchResult")
• id string required
• alias string nullable
• url string required
• name string nullable
• description string nullable
• image string nullable
• manager string nullable
• topic string nullable
• topic_id string nullable
• subtopic string nullable
• subtopic_id string nullable
• region string nullable
• region_id string nullable
• subregion string nullable
• subregion_id string nullable
• keywords array (default: [])
• member_count integer nullable
• post_count integer nullable
• new_post_count integer nullable
• rank_stage integer nullable
• rank_name string nullable
• is_power_cafe boolean nullable
• is_star_cafe boolean nullable
• is_game_cafe boolean nullable
• is_education_cafe boolean nullable
• is_town_cafe boolean 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.