# Naver Map API (Korea) — Naver Place & Map scraper: search Korean businesses (all categories) with full profiles, ratings, visitor & blog reviews, plus Naver search autocomplete

> search restaurants & food places by query (richest food data)
> ReefAPI engine `naver-map` · 7 endpoints · clean JSON, no scraping or browsers to manage.

## How to call
- **Endpoint:** `POST https://api.reefapi.com/naver-map/v1/<action>` with a JSON body.
- **Auth:** header `x-api-key: <YOUR_REEFAPI_KEY>` — create one free (1,000 credits, no card): https://reefapi.com/signup
- **Response (every call):** `{ ok: boolean, data: ..., meta: { record_count, credits, ... }, error: { code, message } }` — branch on `ok`. Failed calls are free.
- **One key + one shared credit pool** across every ReefAPI API. Per-call credits are listed on each endpoint below.
- **Use it from an AI agent (MCP):** connect `https://api.reefapi.com/mcp` (remote streamable-http). Clients that add connectors by URL, such as ChatGPT and the Claude app, connect with OAuth 2.1 (the user pastes their key once on a ReefAPI page; discovery at `/.well-known/oauth-protected-resource/mcp`). Config files send the key as `Authorization: Bearer <key>`. `?key=<key>` in the URL also works as a last-resort fallback.

## Endpoints

### POST https://api.reefapi.com/naver-map/v1/place/search — 1 credit
search restaurants & food places by query (richest food data)

**Parameters:**
- `query` (string, required) — Korean search text (e.g. a business name or 'area + cuisine'). Used to find places, or to resolve a place_id when one isn't given.
- `limit` (integer, optional, default 10) — Maximum number of places to return (1-50).

**Returns:** places[]{name,address,rating,review_count,...}, total, query

**Example request body:**
```json
{
  "query": "강남 맛집",
  "limit": 5
}
```

### POST https://api.reefapi.com/naver-map/v1/place/search-all — 1 credit
search ANY business type on Naver Place/Map (clinics, cafes, hotels, salons, shops…)

**Parameters:**
- `query` (string, required) — Korean search text for ANY business type — clinic, cafe, hotel, salon, shop, hospital, etc. (e.g. '강남 성형외과' = Gangnam plastic surgery).
- `limit` (integer, optional, default 10) — Maximum number of places to return (1-30). The first 10 come from Naver's search-box results; above 10 the rest is filled from the Naver Map result list.

**Returns:** places[]{place_id,name,category,road_address,jibun_address,review_count,has_booking,latitude,longitude}, place_suggestions[], total, query

**Example request body:**
```json
{
  "query": "강남 성형외과",
  "limit": 5
}
```

### POST https://api.reefapi.com/naver-map/v1/place/detail — 1 credit
full place profile (rating, phone, hours, images)

**Parameters:**
- `place_id` (string, required) — Naver Place numeric id (from place/search results or place/resolve).
- `query` (string, optional) — Korean search text (e.g. a business name or 'area + cuisine'). Used to find places, or to resolve a place_id when one isn't given.

**Returns:** place{} — name, category, rating, review_count, phone, hours, address, images

**Example request body:**
```json
{
  "place_id": "18485191"
}
```

### POST https://api.reefapi.com/naver-map/v1/place/reviews — 1 credit
visitor reviews (latest page, ~20 per call) with the true total

**Parameters:**
- `place_id` (string, required) — Naver Place numeric id (from place/search results or place/resolve).
- `limit` (integer, optional, default 50) — Maximum reviews to collect (capped by Naver).
- `page_size` (integer, optional, default 20) — Accepted for compatibility but currently has no effect — reviews come from one page. meta.page_size_supported reports this.
- `sort` (enum, optional, default "recent") — Accepted for compatibility but currently has no effect — reviews arrive in Naver's own page order. meta.sort_supported reports this. [one of: recent, RECENT, RECOMMEND, RATING]
- `query` (string, optional) — Korean search text (e.g. a business name or 'area + cuisine'). Used to find places, or to resolve a place_id when one isn't given.

**Returns:** place_id, place_name, reviews[]{rating,body,visited,created,author}, count, total_reported, capped

**Example request body:**
```json
{
  "place_id": "18485191",
  "limit": 10
}
```

### POST https://api.reefapi.com/naver-map/v1/place/blog-reviews — 1 credit
blog reviews

**Parameters:**
- `place_id` (string, required) — Naver Place numeric id (from place/search results or place/resolve).
- `limit` (integer, optional, default 50) — Maximum blog reviews to collect.
- `page_size` (integer, optional, default 20) — Accepted for compatibility but currently has no effect — reviews come from one page. meta.page_size_supported reports this.
- `query` (string, optional) — Korean search text (e.g. a business name or 'area + cuisine'). Used to find places, or to resolve a place_id when one isn't given.

**Returns:** place_id, reviews[] (blog posts: title, url, snippet, date), count

**Example request body:**
```json
{
  "place_id": "18485191",
  "limit": 10
}
```

### POST https://api.reefapi.com/naver-map/v1/place/resolve — 1 credit
resolve a query → place_id (works for food AND any other business)

**Parameters:**
- `query` (string, required) — Korean search text (e.g. a business name or 'area + cuisine'). Used to find places, or to resolve a place_id when one isn't given.
- `place_id` (string, optional) — Naver Place numeric id (from place/search results or place/resolve).

**Returns:** place_id, name, category, address, review_count, exact_name_match, match_source, candidates[] — the resolved place plus the runner-up matches, so the caller can verify the id belongs to the right branch

**Example request body:**
```json
{
  "query": "강남 맛집"
}
```

### POST https://api.reefapi.com/naver-map/v1/search/autocomplete — 1 credit
Naver search-box keyword suggestions for a partial term (keyword research)

**Parameters:**
- `query` (string, required) — Partial Korean (or English) search term to autocomplete (e.g. '아이폰' → '아이폰17', '아이폰18'…).
- `limit` (integer, optional, default 10) — Maximum number of suggestions to return (1-30).

**Returns:** query, suggestions[]{suggestion}, count

**Example request body:**
```json
{
  "query": "아이폰",
  "limit": 5
}
```

## At scale
- **Volume:** 5M+ requests a day, measured at 60 requests a second across the fleet with no
  central bottleneck. Per-key limits are raised for high-volume accounts; volume pricing on request.
- **Missing a source:** tell us a site we do not cover and it becomes an engine. A customer asked
  for bestprice.gr on 21 Sep 2026 and it was in the catalog on 22 Sep.
- **Support:** 2 minute median time from a question in the live chat to the first answer. Setup
  help included, no support tier to buy.
- **One key, one credit pool** across every API. No per-site plans, no separate subscriptions.

## More
- Try it live, no code: https://reefapi.com/playground?engine=naver-map
- Human docs page: https://reefapi.com/docs/naver-map
- Overview page: https://reefapi.com/naver-map-api
- Every ReefAPI API in one file (for your AI): https://reefapi.com/llms-full.txt

## Questions developers ask about Naver Map data

### How do I get Naver Map results for a keyword like 강남역 맛집 (name, rating, review count) without Selenium?

Developers scraping Naver Map with Selenium report switching into the `searchIframe` for the result list and the `entryIframe` for each place, waiting several seconds per click, and rewriting selectors every time Naver changes the layout.

ReefAPI's Naver API takes the same Korean keyword and returns the Naver Map restaurant list in Naver's order: each place with its `place_id`, category, address, coordinates, visitor `review_count` and star `rating` (`null` when Naver shows no score for that place), plus the `total` number of matches.

```
curl -X POST https://api.reefapi.com/naver/v1/place/search \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"query":"강남역 맛집","limit":3}'
```

Real response, 3 Nov 2026: total 7004 · 1. "닭갈비전 강남점" 닭갈비, rating 4.88, 1,839 reviews · 2. "멕시타이거" 요리주점, rating 4.85, 1,404 reviews · 3. "퀸즈가든 강남역점" 샤브샤브, rating 4.91, 7,816 reviews

### Naver's local search API returns at most 5 places and no ratings. How do I get more Naver Place results?

Naver's documentation for the local search API (`/v1/search/local`) caps `display` at 5 and `start` at 1, so a query never pages past the first five places, and each item carries a name, category, address and map coordinates but no rating, review count or place ID. The Search API is also limited to 25,000 calls a day.

For Naver Place data on any kind of business (cafes, clinics, salons, hotels), ReefAPI's Naver API `place/search-all` returns each match with its Naver Place ID, road and lot-number address, visitor review count, a booking flag and latitude/longitude.

```
curl -X POST https://api.reefapi.com/naver/v1/place/search-all \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"query":"성수동 카페","limit":10}'
```

Real response, 2 Nov 2026: 10 places · "베통 성수" 카페,디저트, 5,625 reviews · "도토리오븐" 4,366 reviews · "성수동대림창고갤러리" 3,961 reviews at 37.5417036, 127.0563952

### How do I find the Naver Place ID for one specific store or branch?

The Naver Place ID is the number in a place link such as `m.place.naver.com/place/1086067689`, and review and detail lookups need it; developers report that the official local search API does not return it.

ReefAPI's Naver API `place/resolve` turns a store name into that ID, says whether the name matched exactly (`exact_name_match`), and lists the runner-up places as `candidates`, so one branch of a chain is not confused with another.

```
curl -X POST https://api.reefapi.com/naver/v1/place/resolve \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"query":"스타벅스 강남R점"}'
```

Real response, 2 Nov 2026: place_id 1086067689 · "스타벅스 강남R점" · 강남대로 390 (역삼동) · 8,265 reviews · exact_name_match true · candidates "스타벅스 압구정R점" 1072718391, "스타벅스 청담스타R점" 487040518

### How can I scrape Naver Place visitor reviews (방문자 리뷰)?

Naver's Search API documents no review fields, so developers who need Naver Place visitor reviews end up opening each place in a browser and reading the review tab inside the `entryIframe`.

ReefAPI's Naver API `place/reviews` takes a place ID and returns the latest page of visitor reviews (about 20): star rating, review text, visit date, posting date, author nickname, photos and the owner's reply, together with the place's real review total and its star distribution.

```
curl -X POST https://api.reefapi.com/naver/v1/place/reviews \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"place_id":"18485191","limit":5}'
```

Real response, 2 Nov 2026: "강남돌곱창" · total_reported 516 · rating 5 · "강남돌곱창에서만 5년이 넘었네요^^ 곱창도 쫄깃하고 신선하게 맛있어서…" · visited 8.13.목 · created 8.19.수 · 5 photos

### How do I get a Naver Place's phone number, opening hours and blog review count?

On Naver Map the full address, hours and phone only appear after you click a result, which is why developers on Inflearn describe crawling store details one click at a time.

ReefAPI's Naver API `place/detail` returns that panel for a place ID: road and lot-number address, phone, star rating, visitor and blog review counts, opening hours for each weekday, amenities, photos and the dishes reviewers mention most. To read the blog posts themselves, `place/blog-reviews` returns each post's title and link.

```
curl -X POST https://api.reefapi.com/naver/v1/place/detail \
  -H "x-api-key: $REEF_KEY" -H "content-type: application/json" \
  -d '{"place_id":"18485191"}'
```

Real response, 2 Nov 2026: "강남돌곱창" · 02-548-7225 · rating 4.76 · 516 visitor / 256 blog reviews · Tue 15:00–23:30 · Sun "정기휴무 (매주 일요일)" · amenities include 주차, 발렛파킹

### How do I collect Naver autocomplete keywords for Korean keyword research?

Korean marketers and developers build small Python tools that pull the keywords Naver suggests under its search box and save them to Excel, as a starting list for Korean keyword research.

ReefAPI's Naver API `search/autocomplete` returns those suggestions for a partial Korean or English term. They are the phrases Naver suggests, in Naver's order, not search volumes.

```
import requests

r = requests.post(
    "https://api.reefapi.com/naver/v1/search/autocomplete",
    headers={"x-api-key": REEF_KEY},
    json={"query": "아이폰", "limit": 10},
)
for s in r.json()["data"]["suggestions"]:
    print(s["suggestion"])
```

Real response, 2 Nov 2026: "아이폰" → 아이폰 듀오 · 아이폰 18프로 · 아이폰18 · 아이폰17 · 아이폰 폴더블 · 아이폰17프로 · 아이폰 se