naver

Search Naver KnowledgeiN (지식iN)

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.

get/naver/kin/search

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/naver/kin/search
  • Auth: API key in header x-api-key

Query parameters

querystring required

Free-text search term (UTF-8). Required.

displayinteger

Number of items to return per page. Defaults to 10, cap 100; display=101 returns 400. Native upstream page-size param. Send the universal limit instead: the API maps it to this name for you.

startinteger

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. Native upstream cursor param. Send the universal cursor instead: the API maps it to this name for you.

sort'sim' | 'date' | 'point'

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.

group'question'

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.

cursorstring

Universal pagination cursor. Send pagination.next_cursor from the previous response back verbatim: the API maps it to this endpoint's native start (offset style). You never construct, decode, or look up a cursor. Omit it for page 1.

limitinteger

Universal page size. The API maps it to this endpoint's native display.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "naver",
  "endpoint": "/v1/naver/kin/search",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  },
  "pagination": {
    "next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsInAiOiJwYWdlIn0",
    "has_more": true,
    "page_size": 30,
    "stopped_at": "known_id"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.