/yodobashi/products/related

POST /api/yodobashi/products/related

Price: 10 credits

Product carousels of a Yodobashi Camera (ヨドバシカメラ) product page: items bought together, items viewed by the same customers, matching accessories, consumables, required options and the item's own variations, each with SKU, name, brand, image and rating.

How to use it

Products shown next to a yodobashi.com product. Pass the 18-digit SKU (or product URL); optionally restrict to one rail: 'bought_together', 'also_viewed', 'accessories', 'consumables', 'required_options' (needed to use the item) or 'variations' (its own colour/size siblings). Each item has id (SKU), url, rail, name, brand, image, rating and review_count.

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: "100000001002968430"; minLength: 1)
• count integer required — Max number of related products to return (min: 1)
• rail string nullable — Keep only one recommendation rail (one of: "bought_together", "also_viewed", "accessories", "consumables", "required_options", "variations")

Response

• @type string (default: "YodobashiRelatedProduct")
• id string required
• url string required
• rail string required
• name string nullable
• brand string nullable
• image string nullable
• rating number nullable
• review_count 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 — Product not found (well-formed SKU but no such product on yodobashi.com) 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.