/yahoo/chiebukuro/questions/answers

POST /api/yahoo/chiebukuro/questions/answers

Price: 20 credits

List every answer to a Yahoo! Chiebukuro question, best answer first: answer id, full text, image, answerer, posting time, なるほど / そうだね / ありがとう counts, AI and low-quality flags and replies

How to use it

The best answer, when the question has one, is the first row with is_best true.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• question string required — Yahoo! Chiebukuro question id or question URL (examples: "1063863160", "https://detail.chiebukuro.yahoo.co.jp/qa/question_detail/q1063863160"; minLength: 1)
• sort string — Order of the answers (default: "newest"; one of: "newest", "oldest", "reactions")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "ChiebukuroAnswer")
• id string required
• question_id string required
• url string required
• text string nullable
• image string nullable
• author object nullable
  • @type string (default: "ChiebukuroUser")
  • id string nullable
  • name string nullable
  • image string nullable
  • url string nullable
  • is_hidden boolean nullable
  • is_enterprise boolean nullable
  • is_professional boolean nullable
  • is_official_ai boolean nullable
  • badges array (default: [])
• is_best boolean (default: false)
• is_ai_generated boolean nullable
• is_low_quality boolean nullable
• is_edited boolean nullable
• helpful_count integer nullable
• agree_count integer nullable
• thanks_count integer nullable
• reply_count integer nullable
• replies array (default: [])
  • @type string (default: "ChiebukuroReply")
  • id string required
  • text string nullable
  • author object nullable
    • @type string (default: "ChiebukuroUser")
    • id string nullable
    • name string nullable
    • image string nullable
    • url string nullable
    • is_hidden boolean nullable
    • is_enterprise boolean nullable
    • is_professional boolean nullable
    • is_official_ai boolean nullable
    • badges array (default: [])
  • posted_at integer nullable
  • is_deleted boolean nullable
• posted_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 — No public Yahoo! Chiebukuro question under that id 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.