querystringrequired
Keyword phrase to search across Naver blogs.
https://api.sandbase.ai/v1/api/naver/blog-searchSearch up to five enriched Naver blog results by keyword with stable cursor pagination: result rank, title, excerpt, post and blogger URLs, blogger name, publish time, and Naver's total match count.
Your output will appear here
Complete the inputs, then click Run.
Search up to five enriched Naver blog results by keyword with stable cursor pagination: result rank, title, excerpt, post and blogger URLs, blogger name, publish time, and Naver's total match count.
curl -X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "naver/blog-search", "sort": "relevance", "limit": 5, "query": "제주도 맛집"}'
The result is returned in outputs[0].data. Lookups that find nothing fail with a not-found error.
| Name | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Keyword phrase to search across Naver blogs. |
cursor | string | No | Opaque pagination cursor from a previous response's nextCursor. |
limit | integer | No | Maximum number of title-enriched posts to return, from 1 to 5 (default 5). |
sort | string | No | Order posts by Naver relevance or newest publication date (default relevance). One of: relevance, recent. |
Billed at the actual cost of each call, about $0.032 per request. A call can cost more when the first data source fails and another one answers. Failed calls and lookups that find nothing are not charged.
Start building
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/blog-search" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"sort": "relevance",
"limit": 5,
"query": "제주도 맛집"
}
SANDBASE_JSON
)
printf '%s\n' "$result"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.
querystringrequiredKeyword phrase to search across Naver blogs.
sortstringOrder posts by Naver relevance or newest publication date (default relevance).
Possible values: relevance, recent
limitintegerMaximum number of title-enriched posts to return, from 1 to 5 (default 5).
cursorstringOpaque pagination cursor from a previous response's nextCursor.
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
| API | Price | Response |
|---|---|---|
Naver Blog SearchThis API Naver | From $0.032 per call | JSON |
Naver | $0.01 per call | JSON |
Naver | $0.015 per call | JSON |
Naver | $0.01 per call | JSON |
Naver | $0.01 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/naver/blog-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.
From $0.032 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: query (string). Optional: sort (one of relevance, recent), limit (integer) and cursor (string). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Naver Blog 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.