# Naver Blog Search (`naver.blog_search`)

Search Korean Naver blog posts by keyword: title, excerpt, blogger, post URL and publish date.

Docs: https://primaryapi.com/docs/api-reference/naver/blog_search

> **Planned.** This API is on the roadmap and cannot be called yet: `POST /v1/run/naver.blog_search` answers `404 not_found`. Ask for it with `POST https://api.primaryapi.com/v1/api-requests` or the MCP tool `send_feedback`.

- Endpoint: `POST https://api.primaryapi.com/v1/run/naver.blog_search`
- Category: Social · Platform: `naver` · Kind: search · Status: planned
- Price: Not priced yet: this API is planned and cannot be called.
- Billing unit: per successful call
- Reliability: routed to a healthy upstream and retried automatically when an attempt fails; live 30-day status: `GET https://api.primaryapi.com/v1/status/apis?sku=naver.blog_search`
- Execution: synchronous (answers 202 only if it outlives the wait window)

## Input

| Field | Type | Required | Default | Constraints | Description |
|---|---|---|---|---|---|
| `query` | string | yes |  | max 500 chars | Keyword phrase to search across Naver blogs, e.g. "강남 맛집". |
| `limit` | integer | no | 5 | 1–5 | Maximum number of results to return (1-5, default 5). |
| `sort` | enum | no | "relevance" | one of: relevance, recent | Order by relevance (default) or newest first. |
| `cursor` | string | no |  |  | Opaque pagination cursor: pass the previous response's nextCursor. |

Unknown fields are rejected with `400 invalid_input`. The routing controls `preferLatencyUnderMs` and `maxCredits` may be sent in the same JSON body.

## Output

When `output.found` is `true`, `output.data` has this shape:

`output.data` is free-form JSON.

When the thing you asked about does not exist (or a search matches nothing) the call still succeeds: `output.found` is `false`, `output.data` is `null` and `output.reason` says why (`not_found`, `private`, `no_results`, …). Misses are free unless the notes below say misses are billed.

## Example request

_Input values are placeholders built from the schema._

```bash
curl -sS -X POST "https://api.primaryapi.com/v1/run/naver.blog_search" \
  -H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"string"}'
```

## Errors to handle

`invalid_input`, `unauthorized`, `insufficient_balance`, `key_limit_reached`, `trial_cap_reached`, `forbidden`, `not_found`, `idempotency_conflict`, `rate_limited`, `all_sources_failed`, `service_unavailable`, `timeout`. See https://primaryapi.com/docs/errors.

## Notes

p2: the official Naver Open API was removed by the verifier: its terms (rev. 2026-10-07) forbid charging users, re-providing, caching or selling Search API results, and new Search API apps closed on 2026-07-30. Revisit after reading the NAVER API HUB price list and terms.

