/naver/kin/questions

POST /api/naver/kin/questions

Price: 5 credits

Get one Naver Knowledge iN question: title, full text, images, category path, tags, asker stats, view, answer, like and comment counts, reward points, and its first answers with author profiles

How to use it

A question is addressed by its category id and document id together; naver/kin/questions/search rows carry both. For every answer of a question use naver/kin/questions/answers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• question string required — Knowledge iN question URL or dirId/docId pair (examples: "https://kin.naver.com/qna/detail.naver?d1id=11&dirId=100508&docId=495245328", "https://m.kin.naver.com/qna/dirs/100508/docs/495245328", "100508/495245328"; minLength: 1)

Response

• @type string (default: "NaverKinQuestion")
• id string required
• dir_id string required
• url string required
• text string nullable
• images array (default: [])
• category string nullable
• category_path string nullable
• parent_category_id string nullable
• parent_category string nullable
• tags array (default: [])
• author string nullable
• author_question_count integer nullable
• author_selection_rate number nullable
• view_count integer nullable
• answer_count integer nullable
• like_count integer nullable
• comment_count integer nullable
• reward_points integer nullable
• has_selected_answer boolean nullable
• has_netizen_pick boolean nullable
• is_legend boolean nullable
• legend_description string nullable
• asker_comment string nullable
• question_type string nullable
• input_device string nullable
• answers array (default: [])
  • @type string (default: "NaverKinAnswer")
  • id string required
  • answer_no integer required
  • question_id string required
  • question_dir_id string required
  • url string required
  • text string nullable
  • images array (default: [])
  • answer_type string nullable
  • is_selected boolean nullable
  • is_netizen_pick boolean nullable
  • is_deleted boolean nullable
  • author string nullable
  • author_type string nullable
  • author_level string nullable
  • author_answer_count integer nullable
  • author_selected_count integer nullable
  • author_profile_image string nullable
  • author_introduction string nullable
  • author_occupation string nullable
  • author_organization string nullable
  • author_company string nullable
  • author_company_homepage string nullable
  • sources array (default: [])
    • @type string (default: "NaverKinAnswerSource")
    • text string nullable
    • url string nullable
  • tags array (default: [])
  • thanks_message string nullable
  • upvote_count integer nullable
  • downvote_count integer nullable
  • like_count integer nullable
  • comment_count integer nullable
  • input_device string nullable
  • created_at integer nullable
  • updated_at integer nullable
• created_at integer nullable
• updated_at integer nullable

Errors

• 422 — question is not a Knowledge iN question URL or dirId/docId pair 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 — No public Knowledge iN question under that dirId/docId pair 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.