/yahoo/chiebukuro/questions/search

POST /api/yahoo/chiebukuro/questions/search

Price: 10 credits

Search Yahoo! Chiebukuro questions by words, status, category and posting window in any of eleven orders: question id, title, snippet, status, answer and view counts, image, category path and times

How to use it

Category ids come from yahoo/chiebukuro/categories; pass a result 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)
• query string required — Words to search for (examples: "パソコン", "犬 しつけ"; minLength: 1)
• status string — Question status (default: "all"; one of: "all", "open", "solved", "voting")
• sort string — Order of the results (default: "relevance"; one of: "relevance", "newest", "oldest", "recently_updated", "least_recently_updated", "most_answers", "fewest_answers", "most_views", "fewest_views", "most_coins", "fewest_coins")
• category string nullable — Chiebukuro category id (examples: "2080401529")
• match_any_word boolean — Match questions containing any of the words (default: false)
• scope string — Text the words are looked for in (default: "question_and_best_answer"; one of: "question_and_best_answer", "question")
• period string — Posting window (default: "any"; one of: "any", "past_24_hours", "past_3_days", "past_7_days")
• posted_from integer nullable — Earliest posting day, unix seconds (day-granular, UTC) (examples: 1262304000)
• posted_to integer nullable — Latest posting day, unix seconds (day-granular, UTC) (examples: 1293753600)
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "ChiebukuroSearchResult")
• id string required
• url string required
• snippet string nullable
• status string nullable
• answer_count integer nullable
• view_count integer nullable
• has_image boolean nullable
• image string nullable
• categories array (default: [])
  • @type string (default: "ChiebukuroCategory")
  • id string required
  • name string nullable
  • parent_id string nullable
  • depth integer nullable
  • url string required
• posted_at integer nullable
• updated_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.