# Naver Kin Search API (https://www.socialcrawl.dev/platforms/naver/kin-search)

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

TL;DR: `GET /v1/naver/kin/search` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## 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. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/naver/kin/search" \
  --data-urlencode "query=코로나 증상" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I use the Naver Kin API to search 지식iN?

Send a GET request to /v1/naver/kin/search with your keyword in the query parameter. The Naver Kin API searches kin.naver.com (Naver's 지식iN Q&A community) and returns the question title, link, and answer description for each match under data.items.

### What is Naver KnowledgeiN and what is it good for?

Naver KnowledgeiN (지식iN) is Korea's dominant public Q&A community, the closest analog to Quora plus Stack Overflow for everyday questions. It is ideal for mining real Korean intent, FAQ topics, and how people phrase problems in their own words.

### What sort options does the KnowledgeiN endpoint support?

sort accepts sim (relevance, the default), date (newest first), and point (by answer points). Sort by point to surface the most-endorsed answers first, which is useful when you want the highest-quality response for a question.

### What fields come back from a KnowledgeiN search?

Each item includes the question title, link to the full thread, and a description that previews the answer, with <b> around matched terms. Naver sends no date, so each row also carries published_at_est, the question's date estimated from its docId and usually within a day.

### How much does the Naver KnowledgeiN API cost?

Each KnowledgeiN search costs 1 credit on the standard tier, regardless of result count. New accounts start with 100 free credits and no credit card, enough to run about 100 Q&A searches while you evaluate the endpoint.

See the full Naver API: https://www.socialcrawl.dev/platforms/naver

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How do I search Naver KnowledgeiN Q&A with an API?
- What is the SocialCrawl Naver Kin API for 지식iN?