/surugaya/products

POST /api/surugaya/products

Price: 5 credits

Get one Suruga-ya (駿河屋) product by its product id or product URL: name, the price Suruga-ya itself asks for every condition it stocks and the price it pays to buy that condition back, manufacturer list price, brand, release date, internal stock number, category breadcrumbs, photos, the free-text product notes, the artist or author profile, the track list of a music release and every category-specific field the shop publishes (model number, voice cast, publisher, imprint, disc count and so on), plus how many other shops sell it and from which price.

How to use it

Fetch one Suruga-ya product by its id (e.g. '604068543', ids are alphanumeric) or a full product URL. Returns id, url, name, image and images, product_type (the shop's own kind-of-product label), department (the catalogue family it belongs to, such as game, dvd, cd, book, figure or toreka), brand, stock_numbers (the shop's management numbers, one per condition), release_date, price (the condition Suruga-ya currently offers), list_price, grades (every condition Suruga-ya itself stocks, each with condition, condition_type new/used/preorder, price, trade_in_price — what the shop pays to buy that condition back — stock_quantity, branch_number and variant_number, and a badge such as newly restocked), is_sold_out, category and category_id (usable as category_id of the search endpoint) with the full categories chain, description, profile, tracklist, details (the raw category-specific table as published), other_offer_count and other_offer_price_from with offers_url. The full price picture across every seller and condition lives on the offers endpoint; this endpoint only shows what Suruga-ya itself sells. A sold-out product is still returned with its metadata. 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)
• product string required — Suruga-ya product id or a full product URL (examples: "604068543", "https://www.suruga-ya.jp/product/detail/604068543")

Response

• @type string (default: "SurugayaProduct")
• id string required
• url string required
• name string nullable
• image string nullable
• images array (default: [])
• product_type string nullable
• department string nullable
• brand string nullable
• stock_numbers array (default: [])
• release_date string nullable
• price number nullable
• list_price number nullable
• currency string (default: "JPY")
• grades array (default: [])
  • @type string (default: "SurugayaGrade")
  • condition string required
  • condition_type string nullable
  • price number nullable
  • trade_in_price number nullable
  • stock_quantity integer nullable
  • branch_number string nullable
  • variant_number string nullable
  • badge string nullable
  • is_selected boolean (default: false)
• is_sold_out boolean (default: false)
• category string nullable
• category_id string nullable
• categories array (default: [])
  • @type string (default: "SurugayaCategoryRef")
  • id string required
  • name string required
• description string nullable
• profile string nullable
• tracklist array (default: [])
• details object (default: {})
  • * string
• other_offer_count integer nullable
• other_offer_price_from number nullable
• offers_url 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 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.