Naver Map Search Scraper
Pricing
$2.00 / 1,000 fetched result pages
Go to Apify Store
Naver Map Search Scraper
Fetch a selected Naver Map result page with addresses, phones, reviews, coordinates, and booking signals.
Fetch a selected Naver Map result page with addresses, phones, reviews, coordinates, and booking signals.
What does this Actor do?
The Actor searches Naver Map for one Korean query and returns one selected result page.
What data does it return?
- Rank, place ID, name, category, and direct links
- Lot and road addresses, phone, image, and coordinates
- Visitor, blog, total review, rating, and save values when available
- Naver Pay, booking, TalkTalk, coupon, delivery, and new-opening signals
- Business hours when returned by Naver
Input
{"query": "강남역 맛집","page": 2,"limit": 50,"x": "127.02306239128518","y": "37.512133585875134"}
| Field | Required | Default | Description |
|---|---|---|---|
query | Yes | - | Korean local-search query. |
page | No | 1 | Result page to fetch. |
limit | No | 30 | Results per page, from 1 to 100. |
sortType | No | 요즘뜨는 | Naver Map's current Place search ordering. Other values are rejected because they are not fields in the current PlaceListInput GraphQL contract. |
x, y | No | Seoul center | Longitude and latitude for the search location. |
failOnError | No | true | Fail the run on a crawler server error. Set false only to store an error row and keep the run successful. |
Output example
{"rank": 1,"placeId": "1234567890","name": "Example Restaurant","roadAddress": "Seoul, Gangnam-gu","phone": "02-000-0000","visitorReviewCount": 320,"hasBooking": true,"total": 226,"query": "강남역 맛집","source": "pcmap_graphql_wtm","schema": "PlaceListInput/placeList","fallbackApplied": false,"proxyUsed": true,"success": true,"httpStatus": 200}
Pricing and limits
- Price: $0.002 per fetched source page ($2 per 1,000 pages)
- Billing event: one successfully fetched Naver Map result page
- Maximum: 100 places on the selected page; Naver can return fewer.
- Actor compute and the KR Residential proxy are included in the event price.
Troubleshooting
- Fewer places than requested: the selected page contains fewer results.
- Unexpected area: provide both
xandy. - Unsupported sort error: the current generic Place GraphQL contract supports only Naver's default ordering. Restaurant-only sort fields are not silently applied to Place search.
Disclaimer
This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Naver.