/naver/kin/questions/search

POST /api/naver/kin/questions/search

Price: 5 credits

Search Naver Knowledge iN questions by words, category and posting window, by relevance, newest or recommended: question and category ids, title, answer snippet, image, tags, answer and like counts, date

How to use it

Pass a row's dir_id and id as dirId/docId to naver/kin/questions for the full question, or to naver/kin/questions/answers for every answer.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Words to search for (examples: "캠핑", "종합소득세"; minLength: 1)
• count integer required — Max number of results (examples: 20; min: 1; max: 900)
• sort string — Order of the results (default: "relevance"; one of: "relevance", "newest", "recommended")
• period string — Posting window (default: "any"; one of: "any", "past_week", "past_month", "past_year")
• created_from integer nullable — Earliest posting day, unix seconds (day-granular, Korea time) (examples: 1704034800)
• created_to integer nullable — Latest posting day, unix seconds (day-granular, Korea time) (examples: 1706626800)
• category_id string nullable — Knowledge iN category id (dirId) (examples: "100508")

Response

• @type string (default: "NaverKinSearchQuestion")
• id string required
• dir_id string required
• url string required
• snippet string nullable
• image string nullable
• category_id string nullable
• category string nullable
• tags array (default: [])
• answer_count integer nullable
• like_count integer nullable
• matched_answer_no integer nullable
• matched_answer_author string nullable
• created_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.