/askul/products/variants

POST /api/askul/products/variants

Price: 10 credits

List every order code in an ASKUL (アスクル) product family: name, price including tax, per-unit price, stock, delivery date, rating, review count, promotion tags and the differentiating attributes (size, pack size, dimensions) of each variant.

How to use it

Expand an ASKUL (アスクル) product family into the individual order codes you can actually order. `family` is the id from askul/products/search (`is_family=true`) or `family_id` of askul/products, or a family URL. `specs` holds exactly the attributes the variants differ by (size, pack size). Feed any returned `id` back into askul/products for the full product record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• family string required — ASKUL product family id or a family URL (examples: "1030", "https://www.askul.co.jp/v/1030/"; minLength: 1)
• count integer required — Max number of variants to return (min: 1)

Response

• @type string (default: "AskulVariant")
• id string required
• url string required
• name string required
• image string nullable
• price_with_tax number nullable
• unit_price_with_tax number nullable
• currency string (default: "JPY")
• in_stock boolean nullable
• delivery_date string nullable
• rating number nullable
• review_count integer nullable
• tags array (default: [])
• specs object (default: {})
  • * string

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 family not found (well-formed family id but no such family on ASKUL) 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.