Naver

Naver is South Korea's dominant search portal. It indexes the Korean web, and especially Korean blogs, community cafes and Q&A, far more deeply than Google does, so for the Korean market it is usually the more meaningful signal.

Base URL: /v1/naver/...

Quickstart

curl "https://www.socialcrawl.dev/v1/naver/blog/search?query=%EC%86%8C%EC%89%AC%EC%96%BC%ED%81%AC%EB%A1%A4&display=10" \
  -H "x-api-key: YOUR_API_KEY"

curl "https://www.socialcrawl.dev/v1/naver/brief?query=%EC%A0%84%EA%B8%B0%EC%B0%A8&corpora=news,blog,cafearticle&include=digest" \
  -H "x-api-key: YOUR_API_KEY"

Search the Korean web

The eight corpora share one response shape but index genuinely different parts of the Korean internet, and picking the wrong one is the most common reason a Korean query comes back thin. All eight are 1 credit.

display defaults to 10 and caps at 100, and start is a 1-indexed offset that caps at 1000. Both reject an out-of-range value with a 400.

Two corpora differ, both because Naver made them differ:

• local caps display at 5 and defaults it to 1, so omitting display returns a single place. It ignores start entirely, which is why it is the one corpus with no pagination. A display above 5 is silently clamped by Naver rather than rejected.
• image additionally takes filter (all, large, medium, small) to restrict results to a size band.

Reach for kin when you want the questions Korean users ask about a topic in their own words, which is a different and often better input to content planning than what marketers wrote about it. Many cafes are members-only, so a cafearticle result may link to a teaser rather than the full post. The title and snippet are still yours.

For news outside Korea use /v1/google_news/search. For Google's version of a Korean place, use /v1/google/business/info.

Clean up Korean input

errata returns an empty string when the query was already correct. This matters more in Korean than in English: Korean mistypes usually come from hitting the wrong jamo key, which produces a syllable that looks nothing like the intended one, so edit-distance correction misses them entirely. Run user-supplied queries through it before searching.

adult returns the string "1" or "0", not a boolean, a detail worth encoding once rather than debugging twice. Use it to moderate user-supplied search input, or to filter a keyword list before publishing it.

One call across the Korean internet

corpora takes a CSV subset when you do not want all five, display sets items per corpus (1-100, default 20), and cursor is the preferred way to page. Prefer it over start.

Read trend data

All three return a time series under data.results[].data[] as {period, ratio} pairs, and all three share the same four optional dimensions: time_unit (date, week, month, default month), device (pc or mo), gender (f or m), and ages. Omit a dimension and you get the total. group_name on search-trend labels the series in the response and defaults to the first keyword.

ratio is a relative index, not a count. It is scaled 0-100 within the window you asked for, so the highest point in your range is always 100. Two separate requests are not comparable to each other, and no endpoint returns absolute search or click volumes. Naver does not publish those.

A keyword or category with no measurable volume returns no data points, and that call is not charged.

Four gotchas worth knowing

Only some endpoints compare, and the rest combine

Which one you get depends on the endpoint, so check before you read the series:

Sending more values than an endpoint accepts returns a 400 naming the limit. We do not silently drop the extras, because a shorter list of series looks identical to "Naver had no data for those".

Setting breakdown on either Shopping Insight endpoint changes the shape again: it splits a single value by device, gender or age instead of comparing several, so only the first category id or keyword you passed is used.

The two Data Lab APIs start at different dates

An earlier start_date is clamped up to the relevant floor rather than rejected, so asking for "everything" is safe on both.

ages uses different codes on different endpoints

This is Naver's own inconsistency, and we surface it rather than silently guess for you:

Sending the wrong set returns a 400 from us before the call is made, so you are never charged for it.

Shopping Insight needs a category id

Naver publishes no category-list API, so the ids have to come from a table. The top-level ones:

Deeper subcategory ids are visible in the URL when you browse a category on Naver Shopping. Pass up to 3 comma-separated ids to compare them, or one id plus breakdown to split it by device, gender, or age.

Retired corpora

Naver shut down its Shopping, Book, and Academic-document search corpora on 31/07/2026 with no grace period and published no replacement API, so /v1/naver/shop/search, /v1/naver/book/search, and /v1/naver/doc/search no longer exist. This was Naver's decision, not ours, and no provider can resell those corpora because the upstream is gone.

If you were using them:

• Shopping listings and prices: there is no API replacement. shopping-insight/category gives you demand and click trends for a category, which covers a lot of the analytical use, but not individual products or prices. For those you would need to scrape shopping.naver.com yourself.
• Books: consider the 알라딘 Open API or Kakao Book Search.
• Academic documents: no comparable open API exists.

brief rejects corpora=shop for the same reason.

All endpoints

14 endpoints available.

Platform notes

• local/search is the one corpus Naver does not paginate. It returns at most 5 places and ignores any offset, so it is a single-page endpoint and returns no pagination cursor. Every other corpus paginates normally up to start=1000.
• sort values are validated per corpus, because Naver's accepted values differ: sim/date for blog, news, cafe and image, plus point on KnowledgeiN, and random/comment on local. encyc and webkr ignore sort entirely. Sending a value the corpus does not accept returns a 400 before the call is made, so it costs you nothing.
• Titles and descriptions come back HTML-tagged with <b> around matched terms, so you can highlight hits directly.
• Korean text is returned as-is, never transliterated or machine-translated. Use brief with include=digest if you want an English synthesis alongside the Korean originals.
• All endpoints use GET with query parameters and return the unified SocialCrawl envelope.

Next steps