querystringrequired
Parameter defines the search query. You can use anything that you would use in a regular Naver search. (e.g., `'query'`, `NOT`, `OR`, `site:`, `filetype:`, `near:`, `ip:`, `loc:`, `feed:` etc.).
Naver Search
https://api.sandbase.ai/v1/api/naver/searchGet Naver web results for a query with organic results, news, blogs, knowledge panels and other Naver sections.
- Price
- $0.01USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 1 required · 8 optional
Playground
Input
Parameter defines the search query. You can use anything that you would use in a regular Naver search. (e.g., `'query'`, `NOT`, `OR`, `site:`, `filetype:`, `near:`, `ip:`, `loc:`, `feed:` etc.).
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`.
The page parameter does the `start` parameter math for you! Just define the page number you want. Pagination starts from 1.
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.
Parameter defines the Search type. This parameter defaults to `nexearch`. Available options: `nexearch`: regular Naver Search, `web`: Naver Web Organic Results, `video`: Naver Video Results, `news`: Naver News Results, `image`: Naver Images API.
Parameter defines how the search results are sorted. This parameter defaults to `0` for Naver News Results, and `r` for other search types. For Naver News Results: `0`: Relevance (default), `1`: Latest, `2`: Oldest (only supported for news). For other search types: `r`: Relevance (default), `dd`: Latest.
Parameter defines the time period for search results. This parameter defaults to `all`. Available options: `all`: search without time restrictions (default), `1h`: 1 hour, `1d`: 1 day, `1w`: 1 week, `1m`: 1 month, `3m`: 3 months, `6m`: 6 months, `1y`: 1 year, Custom date range in the format `fromYYYYMMDDtoYYYYMMDD` (e.g., `from20250801to20250830`). Additional options for Naver News Results only: `2h`: 2 hours, `3h`: 3 hours, `4h`: 4 hours, `5h`: 5 hours, `6h`: 6 hours.
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.
Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
OutputReady
Your output will appear here
Complete the inputs, then click Run.
API README
Naver Search
Get Naver web results for a query with organic results, news, blogs, knowledge panels and other Naver sections.
Request
curl -X POST "https://api.sandbase.ai/v1/api/naver/search" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "커피"}'
The result is returned in outputs[0].data as structured JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Parameter defines the search query. You can use anything that you would use in a regular Naver search. (e.g., 'query', NOT, OR, site:, filetype:, near:, ip:, loc:, feed: etc.). |
start | string | No | 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 fo |
page | string | No | The page parameter does the start parameter math for you! Just define the page number you want. Pagination starts from 1. |
num | string | No | 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 | string | No | Parameter defines the Search type. This parameter defaults to nexearch. Available options: nexearch: regular Naver Search, web: Naver Web Organic Results, video: Naver Video Results, news: Naver News Results, image: Naver Images |
sort_by | string | No | Parameter defines how the search results are sorted. This parameter defaults to 0 for Naver News Results, and r for other search types. For Naver News Results: 0: Relevance (default), 1: Latest, 2: Oldest (only supported for news) |
period | string | No | Parameter defines the time period for search results. This parameter defaults to all. Available options: all: search without time restrictions (default), 1h: 1 hour, 1d: 1 day, 1w: 1 week, 1m: 1 month, 3m: 3 months, 6m: 6 mo |
device | string | No | 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. |
json_restrictor | string | No | Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details. |
Pricing
$0.010 per successful call. Failed calls are not charged.
Start building
Send your first request
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/naver/search" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"query": "커피"
}
SANDBASE_JSON
)
printf '%s\n' "$result"2. Authentication
Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
3. Parameters
startstring
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`.
pagestring
The page parameter does the `start` parameter math for you! Just define the page number you want. Pagination starts from 1.
numstring
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.
wherestring
Parameter defines the Search type. This parameter defaults to `nexearch`. Available options: `nexearch`: regular Naver Search, `web`: Naver Web Organic Results, `video`: Naver Video Results, `news`: Naver News Results, `image`: Naver Images API.
sort_bystring
Parameter defines how the search results are sorted. This parameter defaults to `0` for Naver News Results, and `r` for other search types. For Naver News Results: `0`: Relevance (default), `1`: Latest, `2`: Oldest (only supported for news). For other search types: `r`: Relevance (default), `dd`: Latest.
periodstring
Parameter defines the time period for search results. This parameter defaults to `all`. Available options: `all`: search without time restrictions (default), `1h`: 1 hour, `1d`: 1 day, `1w`: 1 week, `1m`: 1 month, `3m`: 3 months, `6m`: 6 months, `1y`: 1 year, Custom date range in the format `fromYYYYMMDDtoYYYYMMDD` (e.g., `from20250801to20250830`). Additional options for Naver News Results only: `2h`: 2 hours, `3h`: 3 hours, `4h`: 4 hours, `5h`: 5 hours, `6h`: 6 hours.
devicestring
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.
json_restrictorstring
Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
4. Response
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
Related APIs
| API | Price | Response |
|---|---|---|
Naver SearchThis API Naver | $0.01 per call | JSON |
Naver | $0.01 per call | JSON |
Naver | $0.015 per call | JSON |
Naver | From $0.032 per call | JSON |
Naver | $0.01 per call | JSON |
Questions
FAQ
How do I use the Naver Search API?
Send a POST request to https://api.sandbase.ai/v1/api/naver/search with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
How much does the Naver Search API cost?
$0.01 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
What parameters does the Naver Search API accept?
Required: query (string). Optional: start (string), page (string), num (string), where (string), sort_by (string) and period (string) and 2 more. The Parameters table and the Playground on this page list every field.
What does the Naver Search API return?
A JSON response returned in the same HTTP request (synchronous).
Do I need a Naver developer account or API key?
No. Naver Search runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Naver API access separately.