naver.com APInaver.com ↗
Search Naver across web, blog, news, cafe, video, and shopping. Returns titles, links, descriptions, and sources. Includes autocomplete suggestions.
curl -X GET 'https://api.parse.bot/scraper/59b25417-91af-4955-8c05-f24339274634/search' \ -H 'X-API-Key: $PARSE_API_KEY'
Search Naver across multiple content types including web, blog, news, cafe, image, video, and shopping. Returns structured search results with titles, links, descriptions, and sources. Results are paginated with 10 results per page.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (starts at 1). |
| queryrequired | string | Search query string. |
| where | string | Content type to search. Accepts exactly one of: nexearch, blog, news, cafe, image, video, shop. |
{
"type": "object",
"fields": {
"page": "integer",
"query": "string",
"where": "string",
"results": "array of search result objects with title, link, description, and source fields",
"total_results": "integer"
},
"sample": {
"data": {
"page": 1,
"query": "python programming",
"where": "blog",
"results": [
{
"link": "https://blog.naver.com/jazzlubu/224260960970",
"title": "파이썬 독학, Python 프로그래밍으로 컴퓨터 프로그래머 입문 시작",
"source": "진실여포",
"description": "이번 글에서는 파이썬 독학을 시작하려는 분들을 기준으로 Python 프로그래밍을 어떻게 보면 덜 어렵게 느껴지는지..."
}
],
"total_results": 10
},
"status": "success"
}
}About the naver.com API
The Naver API covers 2 endpoints that return structured search results and autocomplete suggestions from Korea's largest search engine. The search endpoint accepts a required query string and an optional where parameter to target one of seven content types — web, blog, news, cafe, image, video, or shopping — returning up to 10 paginated results per page with title, link, description, source, and total_results fields.
Search Endpoint
The search endpoint queries Naver across multiple content types controlled by the where parameter. Accepted values are nexearch (general web), blog, news, cafe, image, video, and shop. Each response includes a results array of objects containing title, link, description, and source, plus top-level page, query, where, and total_results fields. Pagination is handled through the page integer parameter starting at 1, with 10 results returned per page.
Autocomplete Endpoint
The autocomplete endpoint takes a query prefix string and returns up to 10 Korean-language suggestions as a flat suggestions array alongside the original query string. This is useful for building type-ahead search interfaces or discovering how Naver users phrase queries around a topic.
Coverage and Scope
Naver is the dominant search engine in South Korea, indexing Korean-language web content, blog posts (Naver Blog is a major publishing platform in Korea), news articles from Korean outlets, Naver Cafe community posts, and shopping listings. Results reflect the Korean-language web, so queries in Korean will yield the most representative results. The shop content type returns product-level results useful for Korean e-commerce research.
- Monitor Korean news coverage of a brand or topic by querying the
newscontent type and trackingtitleandlinkfields over time. - Build a Korean-language type-ahead search widget using autocomplete
suggestionsresponses. - Aggregate Naver Blog posts about a product category using the
blogcontent type and extractingdescriptionandsourcefields. - Research Korean shopping trends by querying the
shopcontent type and collecting product titles and links. - Track how Korean internet communities discuss a topic by querying the
cafecontent type. - Discover high-volume Korean search query variants by feeding seed terms into the
autocompleteendpoint. - Collect
total_resultscounts across content types to gauge relative interest in a keyword on the Korean web.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Naver have an official developer API?+
What does the `where` parameter control, and what are the valid values?+
where parameter selects the content type searched. Valid values are nexearch (general web results), blog, news, cafe, image, video, and shop. Only one value can be passed per request. Omitting it defaults to general web search.Does the search endpoint return image or video media files directly?+
where is set to image or video, the results array returns title, link, description, and source fields pointing to the content — it does not return binary media, thumbnails, or embeds directly. You can fork the API on Parse and revise it to extract additional media metadata fields if needed.Is there support for filtering search results by date range or sorting by recency?+
search endpoint accepts query, where, and page but no date-range or sort parameters. You can fork the API on Parse and revise it to add date filtering for content types like news or blog where recency is relevant.How deep can pagination go, and is there a cap on total pages retrievable?+
page parameter starts at 1 and each page returns 10 results. The total_results field in the response indicates the full result count. In practice, Naver limits how many pages of results are accessible for any given query, so very high page numbers may return empty result sets regardless of total_results.