Blog search
1 credit/v1/naver/blog/searchSearch Naver Blog.
query, display, start, sort
Naver APISearch Naver data with one API
Fetch public Naver search surfaces as structured JSON with one SocialCrawl API key. Blog, news, cafe, knowledge-in, web, image, local, trends, and shopping insight. Reads are priced in credits.
/v1/naver
14 active endpoints
- GET /v1/naver/blog/search
- GET /v1/naver/news/search
- GET /v1/naver/cafearticle/search
- GET /v1/naver/kin/search
- GET /v1/naver/webkr/search
- GET /v1/naver/image/search
- GET /v1/naver/local/search
- GET /v1/naver/brief
- GET /v1/naver/search-trend
- GET /v1/naver/shopping-insight/keyword
What Naver endpoints does SocialCrawl ship?
14 live read endpoints for public Naver search and insight data. Blog, news, cafe, Kin, web, image, local, brief composite, trends, and shopping insight. Data API only.
News search
1 credit/v1/naver/news/searchSearch Naver News.
query, display, start, sort
Cafe search
1 credit/v1/naver/cafearticle/searchSearch Naver Cafe articles.
query, display, start, sort
Knowledge-iN search
1 credit/v1/naver/kin/searchSearch Naver KnowledgeiN (지식iN).
query, display, start, sort
Web search
1 credit/v1/naver/webkr/searchSearch Naver Web (웹문서).
query, display, start, sort
Image search
1 credit/v1/naver/image/searchSearch Naver Image.
query, display, start, sort, filter
Local search
1 credit/v1/naver/local/searchSearch Naver Local (장소 검색).
query, display, sort
Brief composite
10 credits/v1/naver/briefOne query across the Korean internet (5 Naver corpora) + optional digest.
query, corpora, display, start, sort
Search trend
5 credits/v1/naver/search-trendGet Naver search-volume trend for Korean keywords (검색어트렌드).
keywords, start_date, end_date, time_unit, group_name
Shopping insight keyword
5 credits/v1/naver/shopping-insight/keywordGet Naver Shopping click trend for keywords inside a category (쇼핑인사이트).
category_code, keyword, start_date, end_date, time_unit, device
Naver API14 endpoints supported
View docsReturns Naver Blog posts matching a query: post title, link, a text snippet, the blogger's name and blog link, and the publish date.
Use it for long form Korean blog writing, which is where most Korean product reviews and how to guides live.
GET/v1/naver/blog/search?query=%EC%86%8C%EC%85%9C%ED%81%AC%EB%A1%A4&display=10
query · Free-text search term (UTF-8). Required.
$ curl https://www.socialcrawl.dev/v1/naver/blog/search?query=%EC%86%8C%EC%85%9C%ED%81%AC%EB%A1%A4&display=10 \
-H "x-api-key: sc_YOUR_API_KEY"— · idle
// Running this live needs your own API key — hit "Try it" to see an example responseHow the Naver API works
Naver is a normal SocialCrawl social surface. You call GET /v1/naver/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.
Authenticate every call
Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.
GET with query params
Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.
Pay in credits, not seats
Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.
Read one JSON envelope
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.
The usual integration chain
Most products resolve an account, page content, then deepen only the posts that matter.
01Query
GET /v1/naver/blog/searchKeyword for the Naver surface you need
Pick blog, news, cafe, Kin, or web per job.
02Search page
GET /v1/naver/news/searchRanked hits with titles, snippets, URLs
Page with start/display where the route supports it.
03Brief
GET /v1/naver/cafearticle/searchMulti-corpus rollup via brief when you need several sources
One Prism-style call instead of hand-fanning every corpus.
04Insight
GET /v1/naver/kin/searchTrend or shopping-insight series when demand is the question
Separate from document search endpoints.
request
GET /v1/naver/blog/search
?query=소셜크롤
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_hereresponse envelope
{
"success": true,
"data": { "/* Author | Post | PostList | CommentList | … */": true },
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}What lands in data
Field names match the rest of SocialCrawl where archetypes align.
Authorblog/search
id, username, display_name, avatar_url, bio, followers, url, ext
PostList / Postnews/search
items[].post with id, url, content, engagement, author, published_at, ext
CommentListcafearticle/search
items[] with author, content.text, engagement, published_at when comments ship
Search / Mediakin/search
search hits, media metadata, or transcripts depending on route
Inside the gateway
Same request lifecycle as every other /v1 platform endpoint.
- 01
Edge receives the call
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.
- 02
Validate, then debit
Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.
- 03
Cache or fetch
A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.
- 04
Normalize and return
Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.
Billing rules that matter in production
- Standard live miss: tier cost (often 1 credit)
- Advanced reads: typically 5 credits
- Premium reads: typically 10 credits
- Metered routes: min floor when documented
- Cache hit: 0 credits
- Empty / hard fail: auto-refund
- Bad params: 400, never charged
- No credits: 402, never charged
- Disabled routes: 503, never charged
How we get the data
Naver is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.
What Naver is for this API
Public Naver surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.
How SocialCrawl reaches it
Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.
What leaves our edge
Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.
What we do not ship live
No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.
field map sketch
upstream identity→ author.* / data rootprofile identity and counters
public item payload→ data.*post content and engagement
list / search page→ items[] or hitscomments or search hits when present
What this API is used for
The jobs this API is most often used for.
14active Naver endpoints in the registry
1 / 5 / 10credit ladder across standard, advanced, premium
Korea-native search and brand monitoring
Callers concentrate on profile, content lists, search, and deepen paths on Naver. Naver blog, news, cafe, and Kin search on the same key as global social platforms, plus a brief composite for multi-corpus pulls.
Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.
What people build with the Naver API
The jobs Naver data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Use case examples
Common ways teams put this data to work, and the stack each one tends to run.
Monitoring jobs
Python, cron, Slack botsPoll profiles and feeds on Naver. Alert when engagement velocity jumps.
Research and VoC
Node, notebooks, BI loadsSearch and expand posts for brand, product, and competitor language on Naver.
Backend product jobs
Go, workers, ExplorerWire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.
Call it in two lines
Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.
curl "https://www.socialcrawl.dev/v1/naver/blog/search?query=소셜크롤" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/naver/news/search?query=삼성전자" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Endpoints
What data does the Naver API return?
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Blog SearchSearch Naver BlogNews SearchSearch Naver NewsEncyc SearchSearch Naver EncyclopediaCafearticle SearchSearch Naver Cafe articlesKin SearchSearch Naver KnowledgeiN (지식iN)Local SearchSearch Naver Local (장소 검색)Image SearchSearch Naver ImageWebkr SearchSearch Naver Web (웹문서)ErrataCorrect a mistyped Korean search query (오타변환)AdultCheck whether a Korean search term is adult-only (성인 검색어 판별)Search TrendGet Naver search-volume trend for Korean keywords (검색어트렌드)Shopping Insight CategoryGet Naver Shopping click trend for a category (쇼핑인사이트)Shopping Insight KeywordGet Naver Shopping click trend for keywords inside a category (쇼핑인사이트)BriefOne query across the Korean internet (5 Naver corpora) + optional digest.
Comparison
How does SocialCrawl compare to Naver Open API for Naver data?
Same Naver data, two very different paths. Auth, rate limits, schema, and cost — side by side.
| Feature | SocialCrawl | Naver Open API |
|---|---|---|
| Authentication | Same x-api-key you already use for TikTok, Instagram, and YouTube | Client-id and client-secret pair issued per registered app |
| Setup | One GET request, works the minute you sign up | Requires Naver Developers app registration before the first call |
| Rate limits / quotas | Credit-based, buy what you use instead of hitting a fixed daily ceiling | Daily quota per app (25,000 calls/day for the search API) |
| Response schema | Unified data.items schema shared across 50 platforms | Naver-specific XML/JSON shapes that vary by corpus |
| Pricing | 1 credit per call on every corpus; 100 free credits at signup | Free within quota, genuinely hard to beat for small projects |
| Data coverage | All 8 search corpora behind one consistent endpoint pattern | Same 8 corpora, each with its own parameters and response quirks |
| Maintenance | One integration covers Naver plus 49 other platforms | Separate keys and quota management per app |
Authentication
SocialCrawl
Same x-api-key you already use for TikTok, Instagram, and YouTube
Naver Open API
Client-id and client-secret pair issued per registered app
Setup
SocialCrawl
One GET request, works the minute you sign up
Naver Open API
Requires Naver Developers app registration before the first call
Rate limits / quotas
SocialCrawl
Credit-based, buy what you use instead of hitting a fixed daily ceiling
Naver Open API
Daily quota per app (25,000 calls/day for the search API)
Response schema
SocialCrawl
Unified data.items schema shared across 50 platforms
Naver Open API
Naver-specific XML/JSON shapes that vary by corpus
Pricing
SocialCrawl
1 credit per call on every corpus; 100 free credits at signup
Naver Open API
Free within quota, genuinely hard to beat for small projects
Data coverage
SocialCrawl
All 8 search corpora behind one consistent endpoint pattern
Naver Open API
Same 8 corpora, each with its own parameters and response quirks
Maintenance
SocialCrawl
One integration covers Naver plus 49 other platforms
Naver Open API
Separate keys and quota management per app
FAQ
Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usWhat is the SocialCrawl Naver API?
The SocialCrawl Naver API is a unified wrapper over Naver's official Open API that lets you search 8 Naver corpora (blog, news, encyclopedia, cafe, KnowledgeiN, local, image, and web) with a single x-api-key. Naver is South Korea's #1 search portal, so this is the fastest route to Korean-language data.
Which Naver corpora can I search through the API?
Eight corpora, each on its own endpoint under /v1/naver/{corpus}/search: Blog, News, Encyclopedia (terms), Cafe articles, KnowledgeiN (지식iN Q&A), Local (places), Image, and Web documents. Every corpus returns results in the same unified schema under data.items. Naver retired its Shopping, Book, and Academic-document corpora on 31/07/2026 and published no replacement, so those three are no longer available from any provider.
Do I need a Naver Developers app or client ID to use this?
No. You skip the Naver Developers console entirely. No separate app registration, no client-id/client-secret pair to rotate, and no per-app daily quota to juggle. You authenticate with the same SocialCrawl x-api-key you already use for TikTok, Instagram, and YouTube.
How much does the Naver API cost?
All 14 Naver endpoints cost 1 credit per call on the standard tier. New accounts get 100 free credits with no credit card required, so you can test every corpus several times before you pay anything. Pricing is flat regardless of how many items a search returns.
Does the Naver API cover Korean-language content well?
Yes. Naver indexes the Korean web more deeply than any other engine, including blogs, community cafes, and KnowledgeiN answers that Google barely touches. Titles and descriptions come back HTML-tagged with <b> around matched terms so you can highlight hits.
How is this different from calling the Naver Open API directly?
SocialCrawl removes three friction points the direct route forces on you: app registration, client-id/secret rotation, and per-corpus daily quotas. Calling Naver's Open API directly requires all three. Here you authenticate with one x-api-key and the same unified schema you use across 50 platforms.
What is the best Naver scraper API?
SocialCrawl is the fastest route: all 8 Naver search corpora (blog, news, cafe, KnowledgeiN, local, and more) behind one x-api-key at 1 credit per call. There is no NAVER API HUB application to register or client-secret to rotate, and signup includes 100 free credits with no credit card.
Is there a Naver data API?
Yes. Naver runs an official Open API, now hosted on NAVER API HUB, and SocialCrawl wraps it so you can search 8 Naver corpora, including blog, news, cafe, KnowledgeiN, and local, with the same x-api-key you use for the other 49 platforms. The official route works well once you register an NCP account and an API HUB application and manage client-id/secret pairs and per-corpus quotas; SocialCrawl skips that setup at 1 credit per call, with 100 free credits on signup and no card.
Is scraping Naver data legal?
SocialCrawl returns publicly available Naver data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction — you are responsible for complying with Naver's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.
Naver scraping API vs the official Naver API — what's the difference?
With SocialCrawl there is no app review or approval queue — sign up and call Naver endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.
Ask AI about SocialCrawl