/yahoo/chiebukuro/questions/list

POST /api/yahoo/chiebukuro/questions/list

Price: 10 credits

List the latest Yahoo! Chiebukuro questions, site-wide or in one category, by status and order: question id, title, category, answer count, reward coins, image and AI-question flags, posting time

How to use it

Category ids come from yahoo/chiebukuro/categories; pass a question id to yahoo/chiebukuro/questions.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• status string — Question status (default: "open"; one of: "open", "solved", "unanswered")
• sort string — Order of the questions (default: "newest"; one of: "newest", "oldest", "recently_updated", "least_recently_updated", "most_answers", "fewest_answers", "most_coins")
• category string nullable — Chiebukuro category id (examples: "2080401529")
• count integer required — Max number of results (min: 1; max: 4000)

Response

• @type string (default: "ChiebukuroListedQuestion")
• id string required
• url string required
• category_id string nullable
• category_name string nullable
• answer_count integer nullable
• answer_snippet string nullable
• reward_coins integer nullable
• has_image boolean nullable
• image string nullable
• is_ai_question 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 Chiebukuro category 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.