> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration.

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/docs/api/v1/naver/places/placeid/get>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/docs/api/v1/naver/places/placeid/get.mdx>

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** <https://www.socialfetch.dev/openapi.json>

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages.
- [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples.
- [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths.
- [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install.
- [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 1112 endpoint tools, plus docs_search/docs_read for implementation help.
- [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples.
- [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start.
- [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog.
- [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI).
- [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls).
- [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).
- Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`).

---
# Get Naver place (https://www.socialfetch.dev/docs/api/v1/naver/places/placeid/get)

## Summary

Get a Naver Place: address, phone, hours, menu with prices, photos, ratings and what visitors mention.

**Tags:** `Naver`

## HTTP

- **Method:** GET
- **Path:** `/v1/naver/places/{placeId}`
- **Base URL:** `https://api.socialfetch.dev`

## Capability summary

- **SDK mapping:** `client.naver.getPlace({ placeId: "1195271893" })`
- **Accepted identifiers:** `placeId` (path)
- **Pagination:** none
- **Business outcome field:** `data.lookupStatus` with values `found`, `not_found`

## Credits

- **Base:** 1 credit per successful lookup.
- **Maximum on success (200):** 1 credit.
- **Failed requests (`lookup_failed`, `503`):** not charged.
- **Authoritative field:** `meta.creditsCharged`.

## Authentication

- **`x-api-key`**: API key (`sfk_...`)

## Parameters

### `placeId` (path)

- **Required:** yes
- **Constraints:** type `string`; pattern: `^\d{3,15}$`
- **Description:** The place id, as in `map.naver.com/p/entry/place/<id>` or `m.place.naver.com/restaurant/<id>`, e.g. `1195271893`. A place URL is accepted too.

## Responses (status codes)

- **200**: Naver place card.
- **400**: Invalid request
- **401**: Missing or invalid API key
- **402**: Insufficient credits
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed.
- **503**: Service temporarily unavailable; safe to retry with backoff.

## Response body (200)

Naver place card.

### Field outline

- **data** (required) — type `object`. Endpoint-specific response payload.
  - **lookupStatus** (required) — type `string`; enum: found, not_found. `not_found` when Naver has no such item.
  - **place** (required) — type `object`; nullable. The place when found; otherwise null.
    - **id** (required) — type `string`. Place id.
    - **name** (required) — type `string`. Place name.
    - **category** (required) — type `string`; nullable. Category, e.g. `족발,보쌈`.
    - **categoryCodes** (required) — type `array`. Naver's category codes.
      - _items:_
        - type `string`
    - **businessType** (required) — type `string`; nullable. Naver's business type in the page path, e.g. `restaurant`, `hospital`, `place`.
    - **description** (required) — type `string`; nullable. The owner's description.
    - **address** (required) — type `string`; nullable. Lot-number address (지번).
    - **roadAddress** (required) — type `string`; nullable. Road-name address (도로명).
    - **directions** (required) — type `string`; nullable. How to get there, as the owner wrote it.
    - **phone** (required) — type `string`; nullable. Phone number.
    - **isVirtualPhone** (required) — type `boolean`; nullable. Whether `phone` is Naver's forwarding number.
    - **coordinates** (required) — type `object`; nullable. Where the place is.
      - **latitude** (required) — type `number`. Latitude.
      - **longitude** (required) — type `number`. Longitude.
    - **conveniences** (required) — type `array`. Amenities, e.g. `포장`, `예약`, `무선 인터넷`.
      - _items:_
        - type `string`
    - **facilities** (required) — type `array`. Facilities listed on the information tab.
      - _items:_
        - type `string`
    - **keywords** (required) — type `array`. Keywords the owner set.
      - _items:_
        - type `string`
    - **homepages** (required) — type `array`. Websites and social profiles.
      - _items:_
    - **hours** (required) — type `array`. Opening hours.
      - _items:_
    - **status** (required) — type `string`; nullable. Open status when the page was read, e.g. `영업 중`.
    - **statusNote** (required) — type `string`; nullable. Status detail, e.g. `23:00에 영업 종료`.
    - **rating** (required) — type `number`; nullable. Average visitor rating out of 5.
    - **visitorReviewCount** (required) — type `integer`; nullable. Visitor reviews.
    - **blogReviewCount** (required) — type `integer`; nullable. Blog and cafe reviews that link the place.
    - **imageCount** (required) — type `integer`; nullable. Photos on the place's page.
    - **imageUrls** (required) — type `array`. The top photos.
      - _items:_
        - type `string`
    - **menuImageUrls** (required) — type `array`. Photos of the printed menu.
      - _items:_
        - type `string`
    - **menu** (required) — type `array`. Menu items with prices.
      - _items:_
    - **reviewThemes** (required) — type `array`. What visitor reviews talk about, most mentioned first.
      - _items:_
    - **reviewKeywords** (required) — type `array`. The phrases visitors vote for (`음식이 맛있어요`), most voted first.
      - _items:_
    - **blogReviews** (required) — type `array`. A few blog and cafe reviews Naver shows on the page.
      - _items:_
    - **bookingUrl** (required) — type `string`; nullable. Naver Booking page.
    - **microReviews** (required) — type `array`. One-line highlights Naver shows.
      - _items:_
        - type `string`
    - **url** (required) — type `string`. The place's page.
- **meta** (required) — type `object`. Metadata describing the request and billing outcome.
  - **requestId** (required) — type `string`; minLength: 1. Unique request identifier for tracing this API call.
  - **creditsCharged** (required) — type `integer`; minimum: 0. Credits charged for this request.
  - **version** (required) — type `string`; enum: v1. Public API version that served the response.
  - **stale** (optional) — type `boolean`; enum: true. Present, and `true`, only when the source couldn't be reached and this is the last good answer for the same request instead, up to 24 hours old. Absent on every live answer.
  - **fetchedAt** (optional) — type `string`. When a stale answer (`stale: true`) was originally fetched (ISO 8601, UTC). Absent on every live answer.

### Example JSON (found)

```json
{
  "data": {
    "lookupStatus": "found",
    "place": {
      "id": "1195271893",
      "name": "아랑족발",
      "category": "족발,보쌈",
      "categoryCodes": [
        "220036"
      ],
      "businessType": "restaurant",
      "description": "[아랑족발] 안녕하세요! 매일 직접 삶아 더 맛있는 제주 흑돼지 족발 전문점 아랑족발입니다. 아랑족발이 특별한 3가지 이유 제주 흑돼지 사용: 일반 돼지가 아닙니다. 쫄깃함과 고소함이 남다른 '제주 흑돼지 족발'로만 삶아냅니다. 상시 파격 주류 이벤트: 맛있는 족발에 술이 빠질 수 없죠! [주류 1+1 이벤트] 상시 진행 중입니다. (소주/맥주 맘껏 드세요!) 편리한 주차: 주차 걱정 NO! **[제원공영 주차장 이용 가능]**하여 단체 회식이나 가족 외식에도 편안하게 방문하실 수 있습니다. 잡내 없이 깔끔하고, 식감은 살린 진짜 제주 족발의 맛. 오늘 저녁, 아랑…",
      "address": "제주 제주시 연동 272-27",
      "roadAddress": "제주 제주시 삼무로 46 1층 아랑족발",
      "directions": "제주 흑돼지족발 맛집, 아랑족발! 정성껏 삶아낸 제주 흑돼지족발의 쫄깃한 식감과 깊은 풍미를 아랑족발에서 만나보세요. 담백한 족발과 매콤한 불족발을 함께 즐기는 반반족발은 많은 분들이 찾는 인기 메뉴입니다. 또한 따뜻한 순두부찌개 서비스와 함께 소주 1+1 이벤트도 진행 중이라 더욱 푸짐하게 즐기실 수 있습니다. 가족모임, 친구모임, 회식까지 편하게 즐기기 좋은 곳! 오늘은 아랑족발에서 맛있는 한 끼 어떠세요?",
      "phone": "0507-1319-2208",
      "isVirtualPhone": true,
      "coordinates": {
        "latitude": 33.4897046,
        "longitude": 126.4915836
      },
      "conveniences": [
        "단체 이용 가능"
      ],
      "facilities": [
        "테이크아웃 할인"
      ],
      "keywords": [
        "제주족발"
      ],
      "homepages": [
        {
          "url": "https://www.instagram.com/arangjokbal/",
          "type": "인스타그램"
        }
      ],
      "hours": [
        {
          "day": "매일",
          "open": "10:00",
          "close": "23:00",
          "breaks": [],
          "lastOrder": null,
          "note": null
        }
      ],
      "status": "영업 중",
      "statusNote": "23:00에 영업 종료",
      "rating": 4.97,
      "visitorReviewCount": 2320,
      "blogReviewCount": 1719,
      "imageCount": 141,
      "imageUrls": [
        "https://ldb-phinf.pstatic.net/20260316_93/17736261614942beGt_JPEG/DSC01735.jpg"
      ],
      "menuImageUrls": [
        "https://ldb-phinf.pstatic.net/20251117_11/1763357947651yWMiI_PNG/31566.png"
      ],
      "menu": [
        {
          "name": "[상시] 소주 & 맥주 1+1 🍾",
          "price": "무료",
          "description": "오늘만 하는 이벤트 아닙니다! 아랑족발은 매일매일 1+1!",
          "imageUrl": "https://ldb-phinf.pstatic.net/20260703_10/1783062872842kCaA8_JPEG/IMG_5246.jpg",
          "isRecommended": true
        }
      ],
      "reviewThemes": [
        {
          "label": "맛",
          "count": 1788
        }
      ],
      "reviewKeywords": [
        {
          "label": "음식이 맛있어요",
          "count": 1789
        }
      ],
      "blogReviews": [
        {
          "title": "제주 연동 맛집 | 제주족발맛집 아랑족발 매일 당일 삶는 푸짐한 반반족발 후기",
          "url": "https://m.blog.naver.com/hhyo_log/224464984102",
          "authorName": "log.h",
          "source": "blog",
          "excerpt": "러닝 후 먹는 족발에 막걸리 한잔 ••• 이 조합 참을 수 있는 분 계신가요..? 러닝을 마치고 저녁을 고민하던 와중 발견한 제주시 연동 족발맛집 #아랑족발 소개해드릴께요 매일 당일 삶는 신선한 흑돼지 족발을 찾는다면? 아랑족발 글,사진 @할리 “아랑족발” 제주특별자치도 제주시 삼무로 46 매일 10:00 ~ 23:00 010-****-**** • 전용 주차장 없어 신제주 공영 주차장 이용 추천 • • 네이버, 카카오맵 예약 가능• 아랑족발 외부모습 #제주족발맛집 #제주연동맛집 #제주흑돼지족발 #제주아랑족발 은 연동 삼무로에 위치하고 있어 주변에 식당이나 술집도 많…"
        }
      ],
      "bookingUrl": "https://m.booking.naver.com/booking/6/bizes/1539144",
      "microReviews": [
        "제주 현지인도 추천하는 숨은 맛집"
      ],
      "url": "https://m.place.naver.com/restaurant/1195271893/home"
    }
  },
  "meta": {
    "requestId": "req_naver_places_placeId",
    "creditsCharged": 1,
    "version": "v1"
  }
}
```

### Machine-readable error codes

When an error JSON body is returned, it may include one of these `error.code` values (derived from the OpenAPI schemas for this operation; additional codes may exist at runtime):

- `bad_request`

## Error handling & retries

Interpret HTTP status codes using the descriptions below. Do not assume a JSON body unless the OpenAPI schema defines one for that status.

- **400**: Invalid request **Retry:** Fix the request; retrying the same invalid payload will not help.
- **401**: Missing or invalid API key **Retry:** Fix the API key first; retrying without changes will not help.
- **402**: Insufficient credits **Retry:** Do not retry without resolving billing/credits (retrying the same request will not help).
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed. **Retry:** May be transient; a few retries with backoff are reasonable.
- **503**: Service temporarily unavailable; safe to retry with backoff. **Retry:** Usually safe to retry with exponential backoff and jitter.

### Suggested client defaults

- Send the API key using the `x-api-key` header on every request.
- On `503` (and sometimes `502`), retry with backoff; cap retries and surface a clear error to the user.
- On `402`, surface an actionable billing message rather than blind retries.

## Examples

### TypeScript SDK

```typescript
import { SocialFetchClient } from "@socialfetch/sdk";

const client = new SocialFetchClient({
  apiKey: process.env.SOCIALFETCH_API_KEY!,
});

const result = await client.naver.getPlace({
  placeId: "1195271893",
});

if (!result.ok) {
  console.error(result.error);
} else {
  console.log(result.value.data);
}
```

### Node.js

```javascript
const response = await fetch(
  "https://api.socialfetch.dev/v1/naver/places/1195271893",
  {
    headers: {
      "x-api-key": "YOUR_API_KEY"
    }
  }
);

const data = await response.json();
console.log(data);
```

### cURL

```bash
curl "https://api.socialfetch.dev/v1/naver/places/1195271893" \
  -H "x-api-key: YOUR_API_KEY"
```

### Python

```python
import requests

response = requests.get(
    "https://api.socialfetch.dev/v1/naver/places/1195271893",
    headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()
print(data)
```