Naver API

Naver Blog search API

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.

POST/v1/run/naver.blog_search
Requests
-
30d

Pricing

One price, in dollars

Providers
Fox- served- uptime- p50$36.00/1k reqflat

Call it

Make your first request

import os, requests

res = requests.post(
    "https://api.getanyapi.com/v1/run/naver.blog_search",
    headers={"Authorization": f"Bearer {os.environ['ANYAPI_KEY']}"},
    json={
        "query": ""
    },
)
print(res.json())
Open in
Get a free key
Sample response
{
  "data": {
    "items": [
      {
        "bloggerName": "Example title",
        "bloggerUrl": "https://example.com/page",
        "createdUtc": 12.5,
        "description": "A short example description of this item.",
        "rank": 1,
        "title": "Example title",
        "url": "https://example.com/page"
      }
    ],
    "nextCursor": "example",
    "total": 12500
  },
  "found": true
}
Response interface
interface NaverBlogSearchResponse {
  data: {
    items: {
      bloggerName: string;
      bloggerUrl: string;
      createdUtc: number;
      description: string;
      rank: number;
      title: string;
      url: string;
    }[];
    nextCursor: string | null;
    total: number;
  } | null;
  found: boolean;
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

Request, response, and price

Last verified 2026-09-14 · uptime and latency measured over 30d
POST /v1/run/naver.blog_search
curl -X POST https://api.getanyapi.com/v1/run/naver.blog_search \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit":5,"query":"제주도 맛집","sort":"relevance"}'
FieldTypeExample value
Request body
querystring"제주도 맛집"Keyword phrase to search across Naver blogs.
cursorstringOpaque pagination cursor from a previous response's nextCursor.
limitinteger5Maximum number of title-enriched posts to return, from 1 to 5 (default 5).
sortenum"relevance"Order posts by Naver relevance or newest publication date (default relevance).
Response
dataobjectThe result wrapper, or null when nothing was found.
data.itemsobject[]Blog posts in Naver's requested search order. Populated whenever the provider has data for the entity.
data.items[].bloggerNamestringBlogger display name.
data.items[].bloggerUrlstringPublic root URL for the blog that published the post.
data.items[].createdUtcnumberPublication date as a UTC epoch timestamp in seconds.
data.items[].descriptionstringSearch-result excerpt from the post.
data.items[].rankintegerOne-based rank within this result page.
data.items[].titlestringBlog post title.
data.items[].urlstringPublic blog post URL.
data.nextCursorstringOpaque cursor for the next page, or an empty string when no next page is available.
data.totalintegerNaver's reported number of matching blog posts.
foundbooleanTrue when Naver returned at least one matching blog post.
Price
Price per requestUSD$0.036
Price /1k reqUSD$36.00

FAQ

About the Naver Blog search API

The AnyAPI Naver Blog search API returns Naver blog search data as normalized JSON from one POST call to /v1/run/naver.blog_search. 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. AnyAPI returns one normalized schema whichever source serves it. It costs from $36 per 1,000 requests, in US dollars with no subscription and no monthly minimum.

It costs from $36 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

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. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.