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.

$32.00/1k req, pay per request, no subscription.

What the API returneditems[0]
{
"rank": 1,
"title": "제주도 맛집 추천 BEST 5, 현지인이 알려주는 찐맛집",
"url": "https://blog.naver.com/jejufoodhunter/223456789012",
"description": "제주도 여행 중 꼭 가봐야 할 맛집 5곳을 현지인 기준으로 정리했습니다. 흑돼지구이부터 해물뚝배기까지 후기와 함께 소개합니다.",
"bloggerName": "제주맛집헌터",
"bloggerUrl": "https://blog.naver.com/jejufoodhunter",
"createdUtc": 1790417700,
"language": "ko"
}
Uptime
100.00%
30d · 48 calls
Requests
48
30d · weekly, last 12 wks
Response
2.7s
median · 30d

Pricing

Naver Blog search API pricing

You pay
$320.00
$32.00/1k req, only for what you use. No monthly plan.
Your first 3 requests are free with the $0.10 starting balance.

Call it

Get Naver blog search in one 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": "제주도 맛집",
        "limit": 5,
        "sort": "relevance"
    },
)
print(res.json())
Open in
Get a free key
Sample response

This sample shows 13 of 14 fields. See every field

{
  "found": true,
  "data": {
    "total": 128540,
    "nextCursor": "b:20260928:3",
    "items": [
      {
        "rank": 1,
        "title": "제주도 맛집 추천 BEST 5, 현지인이 알려주는 찐맛집",
        "url": "https://blog.naver.com/jejufoodhunter/223456789012",
        "description": "제주도 여행 중 꼭 가봐야 할 맛집 5곳을 현지인 기준으로 정리했습니다. 흑돼지구이부터 해물뚝배기까지 후기와 함께 소개합니다.",
        "bloggerName": "제주맛집헌터",
        "bloggerUrl": "https://blog.naver.com/jejufoodhunter",
        "createdUtc": 1790417700,
        "language": "ko"
      },
      {
        "rank": 2,
        "title": "서귀포 올레시장 맛집, 갈치조림 노포 다녀온 후기",
        "url": "https://blog.naver.com/sosohantravel/223456781234",
        "description": "서귀포 올레시장 근처 갈치조림 맛집을 다녀왔어요. 웨이팅 30분이었지만 그만한 가치가 있는 맛이었습니다.",
        "bloggerName": "소소한여행일기",
        "bloggerUrl": "https://blog.naver.com/sosohantravel",
        "createdUtc": 1790102400,
        "language": "ko"
      },
      {
        "rank": 3,
        "title": "제주 흑돼지 맛집 3대장 총정리, 웨이팅 없이 가는 법",
        "url": "https://blog.naver.com/blackpigtour/223456770001",
        "description": "제주 흑돼지 맛집 중에서도 줄이 가장 긴 3곳을 비교하고, 웨이팅 없이 방문하는 시간대까지 정리했습니다.",
        "bloggerName": "흑돼지탐방대",
        "bloggerUrl": "https://blog.naver.com/blackpigtour",
        "createdUtc": 1789808700,
        "language": "ko"
      }
    ]
  }
}

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

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-11-14 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • querystring

    제주도 맛집

    Keyword phrase to search across Naver blogs.

  • cursorstring

    Opaque pagination cursor from a previous response's nextCursor.

  • limitinteger

    3

    Maximum 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).

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

each itemdata.items[]

Blog posts in Naver's requested search order. Populated whenever the provider has data for the entity.

  • bloggerNamestring

    제주맛집헌터

    Blogger display name.

  • bloggerUrlstring

    https://blog.naver.com/jejufoodhunter

    Public root URL for the blog that published the post.

  • createdUtcnumber

    1790417700

    Publication date as a UTC epoch timestamp in seconds.

  • descriptionstring

    제주도 여행 중 꼭 가봐야 할 맛집 5곳을 현지인 기준으로 정리했습니다. 흑돼지구이부터 해물뚝배기까지 후기와 함께 소개합니다.

    Search-result excerpt from the post.

  • languagestring

    ko

    Two-letter language code Naver detected for the post text.

  • rankinteger

    1

    One-based rank within this result page.

  • titlestring

    제주도 맛집 추천 BEST 5, 현지인이 알려주는 찐맛집

    Blog post title.

  • urlstring

    https://blog.naver.com/jejufoodhunter/223456789012

    Public blog post URL.

datadata

The result wrapper, or null when nothing was found.

  • nextCursorstring

    b:20260928:3

    Opaque cursor for the next page, or an empty string when no next page is available.

  • totalinteger

    128540

    Naver's reported number of matching blog posts.

top level
  • foundboolean

    true

    True when Naver returned at least one matching blog post.

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

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 $32 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Naver blog search calls through AnyAPI succeeded, with a median response time of 2.7 seconds across 48 measured calls.

It costs from $32 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

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.

Over the last 30 days, 100.0% of Naver blog search calls through AnyAPI succeeded, with a median response time of 2.7 seconds across 48 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 3 Naver Blog search calls at $0.032 each.

Send a POST request to https://api.getanyapi.com/v1/run/naver.blog_search with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.