/yodobashi/products

POST /api/yodobashi/products

Price: 10 credits

Get full Yodobashi Camera (ヨドバシカメラ) product details by SKU or product URL: name, brand, maker, images, price with list price and discount, Gold Point reward, stock and delivery status, alternative editions, description, spec table, category breadcrumbs, category rankings, rating and review count.

How to use it

Fetch one Yodobashi Camera product by its 18-digit SKU (e.g. '100000001002968430') or a full product URL. Returns name, brand, maker (+maker_id for the makers endpoint), image/images, price, list_price, discount, point and point_rate (Gold Point reward), availability (InStock/OutOfStock/LimitedAvailability/Discontinued), is_discontinued, stock_message, delivery_message, release_date (ISO, and for digital items the publication date), category+category_id+breadcrumbs, rating, review_count, variation_skus (sibling colour/size SKUs), formats (the same title in another edition, e.g. print vs e-book, each with its own SKU and price), store_stock_count (physical stores holding it, detailed by the stock endpoint), rankings (position inside a category) and specs (spec table key/values). For a discontinued product price is the last selling price. All prices are in JPY.

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", "https://www.yodobashi.com/product/100000001002968430/"; minLength: 1)

Response

• @type string (default: "YodobashiProduct")
• id string required
• url string required
• name string nullable
• brand string nullable
• maker string nullable
• maker_id string nullable
• description string nullable
• image string nullable
• images array (default: [])
• price number nullable
• list_price number nullable
• discount number nullable
• currency string (default: "JPY")
• availability string nullable
• is_discontinued boolean (default: false)
• condition string nullable
• stock_message string nullable
• delivery_message string nullable
• point integer nullable
• point_rate number nullable
• release_date string nullable
• category string nullable
• category_id string nullable
• breadcrumbs array (default: [])
• rating number nullable
• review_count integer nullable
• store_stock_count integer nullable
• variation_skus array (default: [])
• formats array (default: [])
  • @type string (default: "YodobashiProductFormat")
  • name string required
  • id string nullable
  • url string nullable
  • price number nullable
  • point integer nullable
  • point_rate number nullable
  • is_current boolean (default: false)
• rankings array (default: [])
  • @type string (default: "YodobashiProductRanking")
  • rank integer nullable
  • days_in_top_100 integer nullable
  • category string nullable
  • category_id string nullable
• specs object (default: {})
  • * string
• notes 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 — 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.