Naver Search Engine Results API
/search?engine=naver
API endpoint allows you to scrape the results from Naver search engine via our SerpApi service. Head to the playground for a live and interactive demo.
API Parameters
Pagination
start
Optional
Parameter controls the offset of the organic results. This parameter defaults to 1 (except for the web
).
(e.g. The formula for all searches except the web is start = (page number * 10) - 9
e.g. Page number 3 (3 * 10) - 9 = 21
)
The formula for the web will be start = (page number * 15) - 29
e.g. Page number 3 (3 * 15) - 29 = 16
.
page
Optional
The page parameter does the start
parameter math for you! Just define the page number you want. Pagination starts from 1.
num
Optional
Parameter defines the maximum number of results to return. 50
(default) returns 50 results. Maximum number of results to return is 100
.
Parameter can only be used with Naver Images API.
Where
where
Optional
Parameter defines the Search type. This parameter defaults to nexearch
.
Available options:nexearch
: regular Naver Search,web
: Web organic results,video
: Naver video result,news
: Naver news results,image
: Naver Images Api.
.
Serpapi Parameters
device
Optional
Parameter defines the device to use to get the results. It can be set to desktop
(default) to use a regular browser, tablet
to use a tablet browser (currently using iPads), or mobile
to use a mobile browser (currently using iPhones).
no_cache
Optional
Parameter will force SerpApi to fetch the Naver results even if a cached version is already present. A cache is served only if the query and all parameters are exactly the same. Cache expires after 1h. Cached searches are free, and are not counted towards your searches per month. It can be set to false
(default) to allow results from the cache, or true
to disallow results from the cache. no_cache and async parameters should not be used together.
async
Optional
Parameter defines the way you want to submit your search to SerpApi. It can be set to false
(default) to open an HTTP connection and keep it open until you got your search results, or true
to just submit your search to SerpApi and retrieve them later. In this case, you'll need to use our Searches Archive API to retrieve your results. async and no_cache parameters should not be used together. async should not be used on accounts with Ludicrous Speed enabled.
API Results
JSON Results
JSON output includes structured data for Ad Results, Knowledge Graph, News Results, Video Results, and more.
A search status is accessible through search_metadata.status
. It flows this way: Processing
-> Success
|| Error
. If a search has failed, the error
will contain an error message. search_metadata.id
is the search ID inside SerpApi.
HTML Results
HTML output is useful to debug JSON results or support features not supported yet by SerpApi. HTML output gives you the raw HTML result from Naver.