Skip to main content

Overview

The ScrapeBadger Naver API turns naver.com — the search portal most of South Korea actually uses — into a clean JSON feed. It covers three areas:
  • Search & content — the web SERP, the dedicated web/news/blog/cafe/ Knowledge iN/image/video/clip verticals, and search-box autocomplete, all with resolved destination URLs and absolute publish timestamps.
  • Naver Place — local business search, full place detail with menus and photos, place reviews, and the place photo viewer.
  • Naver Shopping — the ranking and insight feeds (bestsellers, keyword and brand rankings, curated verticals), product and catalog search with price-comparison, SmartStore and Brand Store storefronts, product detail, reviews & Q&A, and the full Shopping Live broadcast/channel/shortclip stack.
All endpoints are GET, live under https://scrapebadger.com/v1/naver/*, and authenticate with the X-API-Key header. Credits are charged per request and reported on the X-Credits-Used response header. A request that returns an empty result, or that Naver answers with a challenge, is not billed.

Features

  • Web & content verticals — the integrated /search SERP plus the dedicated /search/web, /news, /blog, /cafe, /kin (Knowledge iN), /image, /video and /clip feeds, each with resolved destination URLs and absolute publish times.
  • Autocomplete — Naver’s search-box suggestions for 2 credits.
  • Naver Place — local business search, full place detail, reviews and the place photo viewer.
  • Shopping rankings & insight — bestseller, keyword and brand rankings, keyword insight, curated deals/verticals/IT-item feeds, and the ranking category trees.
  • Shopping search & catalog — the finder product search and filter facets, filtered search, the deep full-catalog search, and per-catalog price-comparison across sellers.
  • SmartStore & Brand Stores — store profile, category tree, product listing and per-store bestsellers.
  • Products, reviews & Q&A — full product detail, variant groups, rating summaries, paginated reviews and product Q&A.
  • Shopping Live — broadcast detail/products/counts/replay, channel profile/ products/broadcasts/shortclips, shortclip detail/products, and the live keyword ranking.

Market

Naver serves South Korea only. Results are returned in Korean (ko-KR), ranked for Korean users, and requests exit from a Korean IP. There is no market or country parameter — every endpoint is single-market.

SmartStore vs. Brand Store

The storefront, product, review and Q&A endpoints take a host parameter that selects the storefront platform — smartstore (Naver SmartStore) or brand (Naver Brand Store). Brand Store coverage is the most complete; some SmartStore calls require an extra identifier (channel_uid or checkout_merchant_no) and may return a partial record. Each endpoint page documents its own requirements.

Credits

Costs are charged per request and reported on the X-Credits-Used response header; the live per-endpoint price is also published at /public/pricing. The standard tier is 5 credits, with these exceptions:
The catalog and price-comparison searches (/shopping/search-catalog and /shopping/price-compare) clear Naver’s shopping challenge in a live browser session, so they are the heaviest calls and a page can take up to ~90 seconds.

Quickstart

Other notes

  • Organic url values are final destinations — any Naver redirect wrapper is resolved so you get the real target URL.
  • related_searches[] and place_results[] appear only when Naver serves them for that query.
  • Shopping ids chain together — take a category_id from /shopping/categories, a catalogue nv_mid from a search or ranking feed, and a storefront slug from a product URL to move between the shopping endpoints.
  • Pagination styles vary by endpoint — content verticals use page, storefront and live lists use page/size, and the live channel feeds and the place photo viewer use an opaque cursor. Each page documents its own.

Errors

Start from /autocomplete (2 credits) to expand a seed term into real Naver queries, then run /search on each suggestion.

Run this asynchronously

Calls on this API can run in the background, so you don’t hold a connection open while they work. Add one of these to the call:
An async call is billed once, when it completes. See Async requests and webhooks for webhooks, signatures and the SDK helpers.