Get Naver search results — every block and every tab — as JSON
The Naver Search API returns Naver (네이버, search.naver.com) — Korea's largest search engine — as JSON.
- endpoints
- 11
- credits per call
- 1–3
3 credits per call≈ $3/1,000 calls1,000 free credits, no card
- Apple (대한민국)
- type
- web
- domain
- www.apple.com
- source
- Apple
- 아이폰 - 위키백과 한국어
- type
- web
- domain
- ko.wikipedia.org
- source
- 위키백과 한국어
- iPhone - 나무위키
- type
- web
- domain
- namu.wiki
- source
- 나무위키
11 active endpoints, on 1, 2 and 3 credit tiers.
- POST/naver-search/v1/search3 credits
- POST/naver-search/v1/web3 credits
- POST/naver-search/v1/news2 credits
- POST/naver-search/v1/blog3 credits
- POST/naver-search/v1/cafe3 credits
- POST/naver-search/v1/kin2 credits
- POST/naver-search/v1/images2 credits
- POST/naver-search/v1/videos3 credits
Run the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
Naver Search API
3 of 11 endpoints, ready to run
Naver's integrated results page as JSON: organic results in Naver's own order (web pages, blog and cafe posts, videos, 지식iN answers), power-link ads, the news and image blocks, AI related questions with their sources, shopping cards, local places, related searches and the spelling correction Naver applied.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What Naver Search endpoints does ReefAPI ship?
11 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Every parameter, every allowed value →
Missing a Naver Search endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Naver Search API works
Naver Search is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 632 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Track a keyword across Naver's verticals
Korean searchers read Naver's own verticals — blogs, cafes, 지식iN — as much as the web. One call per vertical gives you the whole picture, each row with a stable URL and an ISO date.
{"query": "다이슨 청소기"}organic_results[] in Naver's order with a type per row (web, blog, cafe, video, kin); ads[] are the power links; shopping_results[] the product cards; sections[] lists every block the page showed.
{"query": "다이슨 청소기", "sort": "date", "page": 2}Newest blog posts first. Naver repeats part of a page on the next one; those rows are removed and repeated_from_previous_page_removed says how many.
{"query": "다이슨 청소기"}Every advertiser bidding on the keyword, 25 per page, with total_ads, title, description, sitelinks and how long the advertiser has run ads.
Rows keyed on the destination URL, with date (as Naver prints it) and date_iso (YYYY-MM-DD in Korean time), and ads always kept apart from organic results.
curl -X POST https://api.reefapi.com/naver-search/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"아이폰"}'{
"ok": true,
"data": { … },
"meta": {
"api": "naver-search",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What each action returns
Measured on 2026-11-06 with live calls. Every action returns the standard envelope; rows below are inside data.
| Action | Rows | Filters and paging |
|---|---|---|
| search | organic_results[], ads[], news[], images[], clips[], related_questions[], ai_overview, shopping_results[], local_results[], related_searches[], sections[], spelling_correction | sort, period or date_from/date_to, spell_check, include_related_searches |
| web | results[] with title, url, displayed_url, snippet, site name, favicon, thumbnail | page (20 per page, up to 20), sort, period or date range, spell_check |
| news | news[] with title, url, naver_news_url, source, date, date_iso, snippet, thumbnail, related_articles[] | page (10 per page, up to 40), sort relevance/date/oldest, period or date range |
| blog | posts[] with title, url, snippet, author, author_url, date, thumbnail, image_count, is_ad | page (up to 10), sort, period or date range |
| cafe | posts[] with title, url, snippet, cafe_name, cafe_id, article_id, date, thumbnail, is_ad | page (up to 5), sort, period, article_type, trade_method, trade_status |
| kin | questions[] with title, url, question_id, question, answer excerpt, answerer, badge, date | page (10 per page, up to 30) |
| images | images[] with image_url (original), thumbnail, source_page, source, width, height, date | page (50 per page, up to 20), sort, period |
| videos | videos[] with url, platform, channel, duration_seconds, views, date, thumbnail, is_short (shorts_only rows carry no duration or views: Naver does not print them on short-form cards) | page (up to 10), sort relevance/date/views, period, duration, shorts_only |
| shopping | products[] with price, original_price, discount_percent, mall, mall_count, rating, reviews, delivery_fee, is_ad | spell_check |
| ads | ads[] with advertiser, displayed_url, title, description, sitelinks[], extensions[], ad_period; total_ads. url and sitelink URLs are Naver's ad click links (ader.naver.com): opening one counts as a paid click; displayed_url is the advertiser's site | page (25 per page, up to 5) |
| autocomplete | suggestions[] in Naver's order | — |
Titles and snippets come back as plain text: Naver's highlight tags and HTML entities are removed. A query Naver answers with no results returns NOT_FOUND; a layout change on Naver's side returns SCHEMA_DRIFT rather than an empty success.
What Naver actually returns, measured
Measured on 2026-11-06 with live calls — Korean and English queries, every action and filter — through the same gateway path customers use.
422 of 422 calls returned rows over two full runs: search 96/96, web 38/38, news 44/44, blog 40/40, cafe 34/34, 지식iN 30/30, images 30/30, videos 28/28, shopping 24/24, ads 28/28, autocomplete 30/30 — 45 Korean and English queries on search plus 12-15 per tab. Median latency 1.2-2.8 s per tab, 3.8 s for the full integrated page.
search returns every block Naver shows: on 아이폰, 20 organic results, 10 power-link ads, 3 news stories with their related-article clusters, 20 images, 20 Naver Clip videos, 4 AI related questions with their sources, 12 shopping cards and 18 related searches. Local-intent queries also carry the place block (7 places for 아이폰 수리, each with the place_id the Naver Place API takes).
Checked live: news sort=date returned 10 of 10 articles from the same day, sort=oldest articles from 1990, a March 2025 range 10 of 10 articles inside it; blog sort=date only posts from the last two days; cafe sort=date the same; video sort=date the newest uploads.
Naver's own blog and video paging repeats part of the previous page (19 of 30 blog posts, 26 of 48 videos, measured). Those rows are removed, so consecutive pages never share a row; a deeper page can therefore hold fewer new rows, and repeated_from_previous_page_removed says how many were dropped.
shopping returns the 8-12 product cards Naver puts on its results page (price-comparison catalogue cards with the lowest price across malls, and Naver Plus Store cards). Naver Shopping's own search site, with hundreds of products per query, is not part of this API.
When Naver searches a corrected query (dkdlvhs becomes 아이폰), spelling_correction says so and spell_check=false searches your exact words. A query Naver itself answers with no results returns NOT_FOUND; an empty answer Naver did not confirm is retried, never reported as no results.
What people build with Naver Search
The jobs this data is most often used for.
endpoints
credits per call
SEO teams track where a site, a blog post or a cafe post ranks on Naver for Korean keywords, tab by tab.
Brand and market researchers follow what Korean blogs, cafes, 지식iN and news say about a product, newest first.
Performance marketers see every advertiser bidding on a Naver keyword, with ad copy, sitelinks and how long they have run ads.
Keyword tools collect Naver autocomplete, related searches and AI related questions to learn how Koreans phrase a topic.
What Naver Search data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 632 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/naver-search/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"아이폰"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/naver-search/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "아이폰"
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Naver Search.
Is this an official Naver API?▾
No. Naver's own Search API for developers needs an application key and returns only part of what the results page shows. ReefAPI is an independent service that returns what Naver's public results pages show, as JSON, with no Naver account.
Is this the same as the Naver Place API?▾
No. The Naver Place engine covers businesses, reviews and the map. This engine is search.naver.com. Its search action does return the place block's place_id, which you can pass to the Naver Place engine for the full profile and reviews.
Do I need a Korean IP?▾
No. You call reefapi.com from anywhere and get the Korean results page, ads and shopping cards included.
Are ads separated from organic results?▾
Yes. Power links are only in ads[]. Paid posts inside the blog and cafe tabs are kept in the list where Naver shows them but carry is_ad: true and no position number. The ads action lists every advertiser on a keyword with Naver's total.
Does it work for English queries?▾
Yes. python tutorial returned 20 organic results, mostly English pages, and Naver's AI briefing with its sources. News, blogs, cafes and 지식iN are Korean services, so English queries return fewer Korean posts there.
How fast is it?▾
Median per call over 422 live calls: autocomplete 1.5 s, 지식iN 1.5 s, news 1.6 s, images 1.7 s, blog 1.7 s, cafe 2.1 s, shopping 2.1 s, web 2.3 s, ads 2.5 s, videos 2.8 s, and 3.8 s for search, which reads the whole integrated page plus related searches. Deeper cafe pages take longer: page N follows Naver's own next-page link N times.
Are the dates exact?▾
date is what Naver prints. date_iso is filled when that is a day: an absolute date, or minutes, hours or days ago. Naver prints older posts as 1주 전 or 2주 전, which is not a day (2주 전 was 9-10 days on the posts' own pages), so those rows carry date_window with the first and last possible day instead. Checked against the posts' own pages: 18 of 18 blog dates and 12 of 12 news dates agreed.
What is the Naver Search API?▾
Naver Search API is a ReefAPI endpoint group for naver (네이버) search results as json: the integrated results page with ads, news, images, ai related questions, shopping cards and places, plus naver web, news, blog, cafe, 지식in, image and video search, the full ad list and autocomplete. It returns live JSON through POST requests under /naver-search/v1.
Is the Naver Search API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Naver Search calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Naver Search login or account?▾
No login to Naver Search is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Naver Search data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Naver Search API use?▾
Naver Search actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Naver Search from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call naver-search actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Naver Search API a Naver Search scraper?▾
It is the managed alternative to a DIY Naver Search scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same naver (네이버) search results as json: the integrated results page with ads, news, images, ai related questions, shopping cards and places, plus naver web, news, blog, cafe, 지식in, image and video search, the full ad list and autocomplete back as clean JSON.
11 Search & SEO APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Naver Search, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 631 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-06.