/surugaya/products/offers

POST /api/surugaya/products/offers

Price: 5 credits

List every shop selling a given Suruga-ya (駿河屋) product: the price, condition and stock of each offer, whether it comes from Suruga-ya itself or from a partner shop, the shop's name, rating, review count and address, the dispatch window, the shop's shipping-fee ladder and when the offer was created and last updated. Offers can be narrowed to one of the five conditions the shop distinguishes (new, used, pre-order, premium and damaged).

How to use it

List all sellers of one Suruga-ya product by its id (the same id the products and search endpoints use). Each offer carries product_id, seller and seller_id (empty for Suruga-ya's own listings, where is_surugaya is true) with seller_url, seller_rating, seller_review_count and seller_address, condition as printed by that seller plus condition_type (new/used/preorder), condition_note, price in JPY, stock_quantity and store_stock_quantity, branch_number and variant_number (which together with seller_id identify the offer), sku, model_number, image, is_free_shipping (whether this item alone already ships free), shipping_tiers (the shop's fee ladder: order_price_from with the shipping fee charged from that order value, as a range where the shop quotes one) and free_shipping_threshold (the order value from which that ladder reaches zero, null when the shop never ships free), shipping_min_days/shipping_max_days, campaign with campaign_ends_at, created_at and updated_at as unix seconds. Filter with condition (all, new, used, preorder, premium, damaged) and order with sort. A product with no seller at all returns an empty list; premium and damaged are conditions partner shops assign and are often empty.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Suruga-ya product id or a full product URL (examples: "112000099", "https://www.suruga-ya.jp/product/detail/112000099")
• count integer required — Max number of offers to return (min: 1)
• condition string — Keep only offers in this condition (default: "all"; one of: "all", "new", "used", "preorder", "premium", "damaged")
• sort string — Offer ordering (default: "price_asc"; one of: "price_asc", "price_desc", "review_count", "free_shipping_first")

Response

• @type string (default: "SurugayaOffer")
• product_id string required
• seller string nullable
• seller_id string nullable
• seller_url string nullable
• seller_rating number nullable
• seller_review_count integer nullable
• seller_address string nullable
• is_surugaya boolean (default: false)
• condition string nullable
• condition_type string nullable
• condition_note string nullable
• price number nullable
• currency string (default: "JPY")
• stock_quantity integer nullable
• store_stock_quantity integer nullable
• branch_number string nullable
• variant_number string nullable
• sku string nullable
• model_number string nullable
• image string nullable
• is_free_shipping boolean (default: false)
• free_shipping_threshold number nullable
• shipping_tiers array (default: [])
  • @type string (default: "SurugayaShippingTier")
  • order_price_from number nullable
  • shipping_fee_min number nullable
  • shipping_fee_max number nullable
• shipping_min_days integer nullable
• shipping_max_days integer nullable
• campaign string nullable
• campaign_ends_at integer nullable
• created_at integer nullable
• updated_at 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 product id but no such product on suruga-ya.jp) 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.