Naver Map Places Scraper
Pricing
from $0.47 / 1,000 place saveds
Naver Map Places Scraper
Extract public Naver Map business listings with addresses, phones, websites, coordinates, categories, review counts, and place URLs.
Naver Map Places Scraper
Pricing
from $0.47 / 1,000 place saveds
Extract public Naver Map business listings with addresses, phones, websites, coordinates, categories, review counts, and place URLs.
Required list of 1–100 entries: Korean search terms such as 카페 or 강남 맛집, numeric place IDs, or full naver.com URLs containing /place/ followed by a numeric ID. Short naver.me links are not resolved as direct lookups. Blank and duplicate entries are removed. Direct lookups return only name, ID and available address, phone and website; most search-only fields remain empty.
Optional city, district or neighborhood appended to keyword searches, for example 서울 or 부산. It is search text, not a geographic boundary, radius or distance filter. Ignored for direct place lookups. The 서울 prefill is a form example, not an API default.
Maximum saved places per query, from 1 to 70; defaults to 10. Naver may return fewer places. Raising this ceiling does not guarantee additional results. Direct place lookups return at most one row. No custom sorting is applied.
Reserved setting; defaults to true. Changing it currently has no effect. Keyword searches return fields exposed in search results; direct lookups always return their smaller set of fields. It does not enable deeper detail or review-text extraction.
The form defaults to proxy disabled (useApifyProxy: false). Explicit proxyConfiguration is passed to the Apify SDK unchanged: retain your existing managed groups/country or custom proxyUrls settings. A false opt-out without custom URLs disables proxy use; custom URLs remain usable with useApifyProxy false. If this field is omitted from raw input, the SDK uses its own default configuration, which may use Apify Proxy; send an explicit false opt-out for direct access. There is no automatic switch or proxy retry after a challenge. Non-object configurations, unsupported keys and non-boolean connection flags are rejected before retrieval. Supported SDK options retain their validation; there is no fallback on validation failure. Proxy use can incur platform usage and does not guarantee access.
{ "useApifyProxy": false}