# Naver Place Reviews API (https://www.socialcrawl.dev/platforms/naver/place-reviews)

> Returns the 20 newest visitor reviews of a Naver Place (or Naver's recommended 20 with `sort=recommended`): review id, full text, masked nickname and profile link, the reviewer's review count, visit day (`published_at`, `YYYY-MM-DD`, Korean date), whether the visit was verified (`verified`, from a receipt, payment or booking) and how (`ext.naver.verified_by`), the treatment or menu item (`ext.naver.treatment`), the visit ordinal, the review's view count, photos, and the owner's reply. Every review carries free sentiment and issue labels. Naver visitor reviews have no star rating, so `rating` is always null. If the main source cannot be read, the call is answered from a second source with the 10 newest reviews instead of 20. Send `since=YYYY-MM-DD` to keep only reviews of visits on or after that day, which is what a daily new-review alert needs; the call costs the same with or without new reviews.

TL;DR: `GET /v1/naver/place/reviews` costs 5 credits per page. The default labels (sentiment, issue) are free. label=reports, incentivized or injection holds 4 extra credits and refunds down to 1 credit per started 25 reviews that were newly judged (the first 100 reviews of a page are judged): reviews already labelled are free, a page where nothing could be judged refunds the whole extra, and a cached page is free. and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `id` | no | The Naver Place id, e.g. 11669922 (the number in the place's link). Send this or url. |
| `url` | no | The place's link as Naver shows it: m.place.naver.com/hospital/11669922/home, map.naver.com/p/entry/place/11669922, or a naver.me share link. Send this or id. |
| `sort` | no | `recent` (default): newest visits first. `recommended`: Naver's own order. (recent \| recommended) |
| `label` | no | Optional CSV of SocialCrawl labels to add to every review. Without this param every page already carries sentiment and issue, free; label= adds the labels you name to them (the defaults keep running). sentiment and issue are free when asked for too; reports, incentivized and injection add 1 credit per started 25 newly judged reviews. judgments=off (or label=none) turns the default labels off. They read the review's title and text, never its stars. sentiment: how the reviewer feels, on five levels (level 0 to 4, score_0_1, confidence), plus rating_mismatch, true when the words clearly contradict the star rating (a glowing text under 1 star, a furious one under 5), null when the review has no rating. issue: the main problem the review reports (label: product_defect, sizing_or_fit, shipping_or_delivery, customer_service, price_or_value, missing_feature, other, or none, with confidence; label is null when unsure). reports (needs reports=): does this review say that the thing you describe happened (p, 0 to 1). incentivized: does the reviewer say they got the product free, discounted or rewarded for the review (p), and did the text carry a disclosure such as 'in exchange for my honest review', Vine or 체험단 (disclosed). injection flags text that addresses an AI system and tries to direct it (flagged, p); it never drops or rewrites a row. These are signals to read, never a verdict on a review or a reviewer. A review that could not be judged carries labels: null. Reviews already labelled for anyone are free, and so is a cached page. data.labels reports what was judged and billed. |
| `reports` | no | Required by label=reports, ignored otherwise. What to look for, in plain words, up to 300 characters, for example reports=the battery drains quickly or reports=배송이 늦음. Every review gains labels.reports.p, the probability that it says so, in any wording or language. Without it label=reports is skipped with the warning label_reports_needs_reports and is not billed. |
| `judgments` | no | Optional, on (the default) or off. By default every row gains free SocialCrawl judgments (computed.labels, and computed.relevance on search endpoints), reported in data.labels (mode default) and data.relevance (origin default), each with a status (complete, partial or skipped) and pending: the rows still being judged when the page was sent, which carry null now and are filled on your next call or cached read. Default judgments never add credits, never change an existing field, and never drop or reorder a row. off returns the page exactly as before, with none of those keys. label=none does the same. (on \| off) |
| `dry_run` | no | Optional. When 1, return a cost preview for this labelled or relevance-filtered request without fetching the page or judging any row. data.estimate reports rows_expected, rows_cached, label_credits_min, label_credits_max and base_credits. 0 credits charged. (1) |
| `label_evidence` | no | Optional, only with label=. When 1, every labelled row also carries computed.labels_evidence.<preset> = { quote, sentence_index }: the sentence in the row that most clearly shows the label, copied verbatim. Absent or null when no single sentence shows it. (1) |
| `fit` | no | Optional. When goal, keep the rows and fields needed for the goal you pass in goal= (plus any that are uncertain, and the first and last), and replace the rest with a stub. data.held_back lists the held ids and a recall id that re-reads the full page from cache at no extra charge. Without this param the page is unchanged. (goal) |
| `goal` | no | Required by fit=goal. What you are trying to do, in your own words, up to 300 characters. |
| `fit_tokens` | no | Optional, only with fit=goal. Soft cap on how much of the page to keep, in tokens. Uncertain blocks and the first and last block are kept even if they exceed it. |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off the page, and the page that reaches one ends the walk: `next_cursor` is not returned and `pagination.stopped_at` is `since`. Sending it sets the newest-first sort shown in this endpoint's sort parameter (any other sort value is a free 400). The page still costs what a page costs, so you pay for the pages you walk and no more. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/naver/place/reviews" \
  --data-urlencode "id=11669922" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### What does the Naver Place Reviews API return?

Returns the 20 newest visitor reviews of a Naver Place with text, visit date, proof of visit, treatment, owner reply, and free sentiment labels. The response uses the same JSON envelope as every SocialCrawl endpoint, with the data, credits_used and request_id fields.

### When should I use the Naver Place Reviews endpoint?

Use it for daily review monitoring: send since to keep only new visits and alert on negative labels.

### How much does the Naver Place Reviews API cost?

The price depends on the request, from 5 to 9 credits per call. Every new account gets 100 free credits. Credits for failed or empty calls are refunded automatically, and there is no subscription.

### What parameters does the Naver Place Reviews API need?

Identify the target with one of id, url. It also accepts 13 optional parameters, all listed on this page. The optional parameter to try first is label (Names the product issue each review raises, at no extra credits; sentiment is free too).

### How do I call the Naver Place Reviews API?

Send a GET request to https://www.socialcrawl.dev/v1/naver/place/reviews?id=11669922 with your API key in the x-api-key header. An Authorization: Bearer header works too.

See the full Naver API: https://www.socialcrawl.dev/platforms/naver

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- What does the SocialCrawl Naver Place Reviews API return?
- How do I get Naver Place Reviews data with the SocialCrawl API?