/yodobashi/products/questions

POST /api/yodobashi/products/questions

Price: 1 credit

Customer questions and answers for a Yodobashi Camera (ヨドバシカメラ) product: question text, post and last-answer dates, answer count, the top answer with its author, purchase date and helpfulness votes.

How to use it

Q&A of one yodobashi.com product, most useful first. Pass the 18-digit SKU (or product URL). Each entry has id, product_id, text, posted_at and last_answer_at (unix seconds), answer_count, author and answer (top answer only: text, posted_at, author, purchased_at, like_count, helpful_yes_count/helpful_no_count, comment_count). A product with no questions returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Yodobashi product SKU (18 digits) or a full product URL (examples: "100000001009750975"; minLength: 1)
• count integer required — Max number of questions to return (min: 1)

Response

• @type string (default: "YodobashiQuestion")
• id string required
• product_id string required
• text string nullable
• posted_at integer nullable
• last_answer_at integer nullable
• answer_count integer nullable
• image string nullable
• author object nullable
  • @type string (default: "YodobashiCommunityUser")
  • name string required
  • image string nullable
• answer object nullable
  • @type string (default: "YodobashiAnswer")
  • id string required
  • text string nullable
  • posted_at integer nullable
  • purchased_at integer nullable
  • purchase_type_code string nullable
  • like_count integer nullable
  • comment_count integer nullable
  • helpful_yes_count integer nullable
  • helpful_no_count integer nullable
  • vote_count integer nullable
  • image string nullable
  • author object nullable
    • @type string (default: "YodobashiCommunityUser")
    • name string required
    • image string 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.