/biccamera/products/ranking

POST /api/biccamera/products/ranking

Price: 5 credits

Get the weekly best-seller ranking of one Bic Camera (ビックカメラ) category: rank, product name, maker, image, price, BicPoint reward, delivery and stock messages, rating and review count.

How to use it

Read the weekly best-seller ranking of a Bic Camera category. category_id is a category path from the categories endpoint (e.g. '001/100/012/045/010'); the upper levels publish a ranking of their own too (e.g. '001/150'), and a narrow shelf can publish fewer entries than the requested count. Each entry has rank, id (usable with the products endpoint), url, name, brand, variant, image, price, point, delivery_message, stock_message, rating, review_count, a short marketing description and period_start/period_end (the sales week the ranking covers, ISO dates). All prices are in JPY and tax-included.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category_id string required — Category path whose ranking to read, e.g. '001/100/012/045/010' (examples: "001/100/012/045/010")
• count integer required — Max number of ranked products to return (min: 1)

Response

• @type string (default: "BiccameraRankingItem")
• id string required
• url string required
• rank integer nullable
• name string nullable
• brand string nullable
• variant string nullable
• image string nullable
• price number nullable
• currency string (default: "JPY")
• point integer nullable
• delivery_message string nullable
• stock_message string nullable
• rating number nullable
• review_count integer nullable
• description string nullable
• period_start string nullable
• period_end 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 — No ranking page for this category path 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.