Naver Kin Search API
Returns question and answer threads from Naver KnowledgeiN: title, link, a snippet, and published_at_est, the question's date estimated from its id (Naver sends none).
GET /v1/naver/kin/searchLast updated November 2026Maintained by the SocialCrawl team
When to use the Naver Kin Search API
Use it to read the real questions Korean users ask about a topic, in their own words.
From the API reference
Searches kin.naver.com. Korea's dominant Q&A community (analog of StackOverflow + Quora for the general public). Returns Q&A threads under data.items[] with title, link, and description (typically a question or answer excerpt). Each row also carries the unified post object beside those keys, as blog and cafe rows do: post.ext.title and post.content.text with Naver's <b> highlight tags removed, post.url, post.ext.question_id (the question's docId) and post.ext.answer_no. Naver returns one row per answer, so the same question can fill several rows; send group=question for one row per question. Naver sends no date, so each row also carries published_at_est (YYYY-MM-DD, Korea time) with date_basis: "kin_docid_estimate": the question's date estimated from its docId, which rises with time, against question pages whose posted date we read. Measured on held-out pages it is usually within a few days; it is an estimate, never a published date, and a question older than the table carries none. The same estimate is on post.ext.published_at_est; post.published_at stays null.
Searching 69 platforms in parallel
What can you do with the Kin Search API?
The Kin Search endpoint gives you structured Naver data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
# GET /v1/naver/kin/search: 1 credit per page. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
# --max-time 60: the API's own time limit for this endpoint.
# --retry 3: retries timeouts, 429 and 5xx, honoring Retry-After.
# -o response.json keeps only the final attempt's body.
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
# Next page: send pagination.next_cursor back as cursor until pagination.has_more is false.
IDEMPOTENCY_KEY=$(od -An -N16 -tx1 /dev/urandom | tr -d ' \n')
curl -sS --max-time 60 --retry 3 -o response.json \
-H "x-api-key: YOUR_API_KEY" \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://www.socialcrawl.dev/v1/naver/kin/search?query=%EC%BD%94%EB%A1%9C%EB%82%98+%EC%A6%9D%EC%83%81&display=10" && cat response.json# GET /v1/naver/kin/search: 1 credit per page. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
import os
import random
import time
import uuid
import requests
API_KEY = os.environ.get("SOCIALCRAWL_API_KEY", "YOUR_API_KEY")
TIMEOUT_S = 60 # the API's own time limit for this endpoint.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/naver/kin/search"
def backoff(attempt):
# Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
return 2 ** attempt * (0.5 + random.random() / 2)
def socialcrawl(params):
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
idempotency_key = str(uuid.uuid4())
for attempt in range(MAX_RETRIES + 1):
try:
res = requests.get(
URL,
params=params,
headers={"x-api-key": API_KEY, "Idempotency-Key": idempotency_key},
timeout=TIMEOUT_S,
)
body = res.json()
except (requests.RequestException, ValueError):
# A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if attempt == MAX_RETRIES:
raise
time.sleep(backoff(attempt))
continue
if body["success"]:
return body
error = body["error"]
# Branch on error["type"], never on the message text.
if error["type"] == "RESOURCE_NOT_FOUND":
return None # refunded: nothing to read
retry_after = res.headers.get("Retry-After")
# SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
permanent = error["type"] == "SERVICE_UNAVAILABLE" and retry_after is None
if not error.get("retryable") or permanent or attempt == MAX_RETRIES:
raise RuntimeError(f"{error['type']}: {error['message']} (request_id {body['request_id']})")
# Retry-After (seconds) wins; otherwise back off.
time.sleep(float(retry_after) if retry_after else backoff(attempt))
params = {
"query": "코로나 증상",
"display": "10",
}
# Walk the list: send pagination.next_cursor back as cursor until has_more is false.
MAX_PAGES = 10 # each page is one call
items = []
for _ in range(MAX_PAGES):
body = socialcrawl(params)
if body is None:
break
items.extend(body["data"]["items"])
page = body.get("pagination") or {}
if not page.get("has_more") or not page.get("next_cursor"):
break
params["cursor"] = page["next_cursor"]
print(f"{len(items)} items")// GET /v1/naver/kin/search: 1 credit per page. Cache hits are free and failed calls are refunded.
// Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
const API_KEY = process.env.SOCIALCRAWL_API_KEY ?? "YOUR_API_KEY";
const TIMEOUT_MS = 60_000; // the API's own time limit for this endpoint.
const MAX_RETRIES = 3;
type Page = { next_cursor: string | null; has_more: boolean };
type SocialCrawlResponse =
| { success: true; data: any; pagination?: Page; credits_used: number; request_id: string }
| { success: false; error: { type: string; message: string; retryable: boolean }; request_id: string };
const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
// Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
const backoffMs = (attempt: number) => 2 ** attempt * 1000 * (0.5 + Math.random() / 2);
async function socialcrawl(url: URL) {
// One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
const idempotencyKey = crypto.randomUUID();
for (let attempt = 0; ; attempt++) {
let res: Response;
let body: SocialCrawlResponse;
try {
res = await fetch(url, {
headers: {
"x-api-key": API_KEY,
"Idempotency-Key": idempotencyKey,
},
signal: AbortSignal.timeout(TIMEOUT_MS),
});
body = (await res.json()) as SocialCrawlResponse;
} catch (error) {
// A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if (attempt >= MAX_RETRIES) throw error;
await sleep(backoffMs(attempt));
continue;
}
if (body.success) return body;
// Branch on error.type, never on the message text.
if (body.error.type === "RESOURCE_NOT_FOUND") return null; // refunded: nothing to read
const retryAfter = res.headers.get("Retry-After");
// SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
const permanent = body.error.type === "SERVICE_UNAVAILABLE" && retryAfter === null;
if (!body.error.retryable || permanent || attempt >= MAX_RETRIES) {
throw new Error(`${body.error.type}: ${body.error.message} (request_id ${body.request_id})`);
}
// Retry-After (seconds) wins; otherwise back off.
await sleep(retryAfter ? Number(retryAfter) * 1000 : backoffMs(attempt));
}
}
const url = new URL("https://www.socialcrawl.dev/v1/naver/kin/search");
url.searchParams.set("query", "코로나 증상");
url.searchParams.set("display", "10");
// Walk the list: send pagination.next_cursor back as cursor until has_more is false.
const MAX_PAGES = 10; // each page is one call
const items: unknown[] = [];
for (let page = 0; page < MAX_PAGES; page++) {
const body = await socialcrawl(url);
if (!body) break;
items.push(...body.data.items);
const next = body.pagination?.next_cursor;
if (!body.pagination?.has_more || !next) break;
url.searchParams.set("cursor", next);
}
console.log(`${items.length} items`);Parameters
| Parameter | Required | Description |
|---|---|---|
| query | Yes | Free-text search term (UTF-8). Required. |
| display | No | Number of items to return per page. Defaults to 10, cap 100; `display=101` returns 400. |
| start | No | 1-indexed offset for pagination. Defaults to 1, cap 1000; `start=1001` is a 400 that costs nothing, and the page that reaches rank 1000 is the last one (`has_more: false`). Past rank 100, `sim` and `point` pages repeat Naver's top 100: those rows are removed and counted in `_warnings` (`recycled_rows`), and an emptied page is free. Page deeper with `sort=date`. |
| sort | No | Sort order. Accepted values: sim|date|point. Defaults to `sim` (relevance) when the corpus supports sort. Values outside this corpus's domain are rejected with a 400 before any upstream call. `date` lists the newest first, but Naver serves only the first 1,000 rows of a query (`start` caps at 1000), so on a common word it reaches back hours or days, not months, and on a multi-word query Naver also loosens the match. (sim | date | point) |
| group | No | Send `question` to get one row per question. Naver returns one row per answer, so a question with three matching answers fills three rows; grouped, its best-ranked row stands for it and carries `answers_on_page` and `post.ext.answer_nos`. Grouping is within the page, the price is unchanged, and paging still advances by the rows Naver served. (question) |
| max_pages | No | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| max_items | No | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| max_credits | No | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |
What does the Naver Kin Search API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"success": true,
"platform": "naver",
"endpoint": "/v1/naver/kin/search",
"data": {
"items": [
{
"title": "멀쩡하다가 갑자기 <b>코로나</b>19 <b>증상</b>이 나타날 수 있나요?",
"link": "https://kin.naver.com/user_d7bfe3/detail.naver?dirId=7010107&docId=495281960&answerNo=1",
"description": "<b>코로나</b>19의 <b>증상</b> 발현 시점은 개인별로 차이가 있으며, 잠복기는 일반적으로 수일 범위로 알려져 있습니다. [출처: 세계보건기구(WHO), 질병관리청 호흡기감염병 정보] <b>증상</b>만으로는 구별하기 어려움: 오한·기침·발열·몸살은 <b>코로나</b>19와... "
},
{
"title": "환절기에 생긴 감기 <b>증상</b>도 독감·<b>코로나</b> 검사가 필요한가요....",
"link": "https://kin.naver.com/user_d7bfe3/detail.naver?dirId=70101&docId=495003976&answerNo=3",
"description": "네, 일반 감기와 독감(인플루엔자), <b>코로나</b>19는 목 통증·콧물·기침처럼 <b>증상</b>이 겹치기 때문에 <b>증상</b>만으로 정확히 구분하기는 어렵습니다. <b>코로나</b>19도 가벼운 감기처럼 시작할 수 있습니다. 특히 지금처럼 주변에 호흡기 환자가 많고... "
}
],
"total": 552336,
"dropped": 0
},
"credits_used": 1,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMTEiLCJlIjoibmF2ZXIva2luL3NlYXJjaCIsInAiOiJzdGFydCJ9",
"has_more": true,
"page_size": 10
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T12:40:55.168Z",
"redacted": true
}Live sample illustrating the unified response shape. Field values reflect the record you query.
How does the Naver Kin Search API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 69 platforms covering 10B+ monthly active users.
One schema, every platform
Query 69 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I use the Naver Kin API to search 지식iN?
What is Naver KnowledgeiN and what is it good for?
What sort options does the KnowledgeiN endpoint support?
What fields come back from a KnowledgeiN search?
How much does the Naver KnowledgeiN API cost?
Ask AI about SocialCrawl
Ready to scrape Naver Kin Search data?
Get your API key and start pulling Naver data in under 60 seconds.
