POST /api/yahoo/chiebukuro/questions
Price: 10 credits
Get one Yahoo! Chiebukuro question: title, full text, image, status, asker, category path, answer, view and empathy counts, reward coins, the best answer with the asker's thanks and the first answers
For every answer of a question use yahoo/chiebukuro/questions/answers.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)question string required — Yahoo! Chiebukuro question id or question URL (examples: "11312911376", "https://detail.chiebukuro.yahoo.co.jp/qa/question_detail/q11312911376"; minLength: 1)@type string (default: "ChiebukuroQuestion")id string requiredurl string requiredtext string nullablesupplement string nullableimage string nullablestatus string nullableauthor object nullable@type string (default: "ChiebukuroUser")id string nullablename string nullableimage string nullableurl string nullableis_hidden boolean nullableis_enterprise boolean nullableis_professional boolean nullableis_official_ai boolean nullablebadges array (default: [])categories array (default: [])@type string (default: "ChiebukuroCategory")id string requiredname string nullableparent_id string nullabledepth integer nullableurl string requiredanswer_count integer nullableview_count integer nullableempathy_count integer nullablereward_coins integer nullablebest_answer object nullable@type string (default: "ChiebukuroAnswer")id string requiredquestion_id string requiredurl string requiredtext string nullableimage string nullableauthor object nullable@type string (default: "ChiebukuroUser")id string nullablename string nullableimage string nullableurl string nullableis_hidden boolean nullableis_enterprise boolean nullableis_professional boolean nullableis_official_ai boolean nullablebadges array (default: [])is_best boolean (default: false)is_ai_generated boolean nullableis_low_quality boolean nullableis_edited boolean nullablehelpful_count integer nullableagree_count integer nullablethanks_count integer nullablereply_count integer nullablereplies array (default: [])@type string (default: "ChiebukuroReply")id string requiredtext string nullableauthor object nullable@type string (default: "ChiebukuroUser")id string nullablename string nullableimage string nullableurl string nullableis_hidden boolean nullableis_enterprise boolean nullableis_professional boolean nullableis_official_ai boolean nullablebadges array (default: [])posted_at integer nullableis_deleted boolean nullableposted_at integer nullablethanks_message string nullableanswers array (default: [])@type string (default: "ChiebukuroAnswer")id string requiredquestion_id string requiredurl string requiredtext string nullableimage string nullableauthor object nullable@type string (default: "ChiebukuroUser")id string nullablename string nullableimage string nullableurl string nullableis_hidden boolean nullableis_enterprise boolean nullableis_professional boolean nullableis_official_ai boolean nullablebadges array (default: [])is_best boolean (default: false)is_ai_generated boolean nullableis_low_quality boolean nullableis_edited boolean nullablehelpful_count integer nullableagree_count integer nullablethanks_count integer nullablereply_count integer nullablereplies array (default: [])@type string (default: "ChiebukuroReply")id string requiredtext string nullableauthor object nullable (see schema ChiebukuroUser)posted_at integer nullableis_deleted boolean nullableposted_at integer nullableposted_at integer nullabledeadline_at integer nullable422 — question is not a Chiebukuro question id or URL 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.