What you get#
Onekey exposes Naver as 14 endpoints behind one API key: 3 endpoints return one record (data is an object) and 11 endpoints return a list (data is an array). Every answer uses the same envelope (success, data, metadata, error), the cost is reported in metadata.credits_charged, and fields are mapped onto the unified schema so the code you write for Naver also works for the rest of the ai & search category.
Endpoints#
| Endpoint | What it does | Parameters | Credits | Status |
|---|---|---|---|---|
adult | Check whether a Korean search term is adult-only (성인 검색어 판별). | query* | 1 | beta |
blog | Naver Blog card (blog name, description, profile image) by blog id. | handle* | 1 | stable |
blog_search | Search Naver Blog posts. | query*, display | 1 | beta |
cafearticle_search | Search Naver Cafe articles. | query*, display | 1 | beta |
encyc_search | Search Naver Encyclopedia entries. | query*, display | 1 | beta |
errata | Correct a mistyped Korean search query (오타변환). | query* | 1 | beta |
image_search | Search Naver Images. | query*, display | 1 | beta |
kin_search | Search Naver KnowledgeiN (Q&A) posts. | query*, display | 1 | beta |
local_search | Search Naver Local places. | query*, display | 1 | beta |
news_search | Search Naver News. | query*, display | 1 | beta |
search_trend | Naver search-volume trend (relative ratio over time) for a Korean keyword. | keywords*, start_date*, end_date*, time_unit | 1 | beta |
shopping_insight_category | Naver Shopping click trend (relative ratio) for a category. | category_code*, start_date*, end_date*, time_unit | 1 | beta |
shopping_insight_keyword | Naver Shopping click trend (relative ratio) for a keyword inside a category. | category_code*, keyword*, start_date*, end_date*, time_unit | 1 | beta |
webkr_search | Search Naver Web documents. | query*, display | 1 | beta |
A * marks a required parameter. Each endpoint name links to its reference page with the full parameter table, caching window and a recorded response.
Make a request#
This calls naver.blog (1 credit, stable). Replace YOUR_API_KEY with your key; sign up, no card. 1,000 free credits cover the open-platform endpoints. Hard-to-reach platforms (X, TikTok, Instagram, Reddit, and others marked on their page) need a verified email and a purchased pack.
curl "https://api.onekey.dev/v1/naver/blog?handle=blogpeople" \
-H "x-api-key: YOUR_API_KEY"Fields you get back#
These unified fields come back from Naver, with the same names as on every other platform. The count is how many of its 14 mapped endpoints return the field; a field the source lacks is null, never missing. 4 platform-specific fields (ext.<name>) come on top, documented on each endpoint page.
| Field | Type | Endpoints |
|---|---|---|
content.text | string | 7 |
content.title | string | 7 |
content.url | URL | 6 |
content.createdAt | ISO 8601 date | 4 |
author.displayName | string | 2 |
author.url | URL | 2 |
entity.name | string | 2 |
entity.url | URL | 2 |
media.thumbnailUrl | URL | 2 |
author.avatarUrl | URL | 1 |
author.bio | string | 1 |
entity.category | string | 1 |
entity.description | string | 1 |
media.height | integer | 1 |
media.url | URL | 1 |
media.width | integer | 1 |
place.address | string | 1 |
The full schema is in Unified schema.
Pricing#
Every Naver endpoint costs 1 credit per call. Free when served from cache (0.2 credit for a cached response over 100 KB). Invalid, failed or not-found calls are not charged. See pricing for credit packs.