/naver/place/places/search

POST /api/naver/place/places/search

Price: 20 credits

Search Naver Places (local businesses) by query. Returns name, category, address, rating, reviews.

How to use it

Search Naver Places (local businesses) by keyword, optionally including a region in the query text. Returns each place's name, category, road and lot addresses, coordinates, phone, visitor rating and review counts, blog review count, cover image, amenities, booking availability, and a short review snippet.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Place search query (examples: "제주 맛집"; minLength: 1)
• count integer required — Max number of results (examples: 20; min: 1; max: 50)

Response

• @type string (default: "NaverPlace")
• id string required
• name string required
• place_url string required
• category string nullable
• business_category string nullable
• category_codes array (default: [])
• micro_review string nullable
• road_address string nullable
• address string nullable
• full_address string nullable
• region string nullable
• latitude number nullable
• longitude number nullable
• phone string nullable
• virtual_phone string nullable
• rating number nullable
• visitor_review_count integer nullable
• text_review_count integer nullable
• blog_review_count integer nullable
• image string nullable
• images array (default: [])
• image_count integer nullable
• conveniences array (default: [])
• payment_info array (default: [])
• has_booking boolean (default: false)
• has_npay boolean (default: false)
• booking_url string nullable
• talktalk_url string nullable
• broadcast_program string nullable
• is_michelin boolean (default: false)
• save_count 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.