/biccamera/products/stock

POST /api/biccamera/products/stock

Price: 5 credits

Get the in-store availability of one Bic Camera (ビックカメラ) product across the chain: store, prefecture, region, stock line, whether the shop keeps a demo unit on the shop floor, when the item can be made ready and whether it can be reserved online for in-store pickup.

How to use it

Check which Bic Camera shops hold one product, by item id or item URL. Each entry has store_id (the store code accepted by the stores endpoint, absent for partner shops on other sites), store_name, store_url, prefecture, region, stock_message (the shop's own wording for in stock, low stock or out of stock), is_on_display (the shop keeps a demo unit on the shop floor; null where the product is of a kind that is never put on display), availability_message (when the item can be made ready) and is_reservable. A product the shops never carry 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 — Bic Camera item id (6-9 digits) or a full item URL (examples: "14458601", "https://www.biccamera.com/bc/item/14458601/")

Response

• @type string (default: "BiccameraProductStock")
• store_id string nullable
• store_name string required
• store_url string nullable
• prefecture string nullable
• region string nullable
• stock_message string nullable
• is_on_display boolean nullable
• availability_message string nullable
• is_reservable boolean (default: false)

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 item id but no such product on biccamera.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.