Catalog

Naver API

Naver data through one normalized API - per-request USD pricing and no subscriptions.

Endpoints1Providers1From · blog search$32.00/1k req · FoxFull breakdownRead docs
Uptime
100.00%
30d · 48 calls
Requests
48
30d · weekly, last 12 wks
Response
2.7s
median · 30d

Call the Naver API

Base URLhttps://api.getanyapi.com
Auth headerAuthorization: Bearer $ANYAPI_KEY
Example request: 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 '{"query":"제주도 맛집","limit":5,"sort":"relevance"}'

Measured performance

What the Naver API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

100.0%
of calls succeeded (48 calls)
Succeeded on first lane 100.0%
Response time (48 calls)
Typical (p50)
2.7s
Half of requests finish within 2.7s
p99 response time
4.2s
p99 response time: 99% of requests finish within 4.2s
Free tools

Run Naver data in the browser

The same public data, with no key and no account, before you write any code.

Or browse every free tool.

FAQ

About the Naver API

The AnyAPI Naver API returns Naver data as normalized JSON across 1 endpoint: blog search. You call one endpoint per job with a single key, and AnyAPI returns one normalized schema whichever source serves it. Pricing is in US dollars, from $32 per 1,000 requests, with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Naver calls through AnyAPI succeeded, with a median response time of 2.7 seconds across 48 measured calls.

Pricing is in US dollars, from $32 per 1,000 requests, 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.

One endpoint: blog search. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Naver endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Naver 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.