/tsukumo/products

POST /api/tsukumo/products

Price: 5 credits

Get full TSUKUMO (ツクモ) product details by product number or product URL: name, maker, tax-included price, availability and condition, stock and dispatch lines, purchase limit, merchandising labels, release date, the marketing copy, every photo, the category trail, the specification table, the manufacturer's own extended specification table, and the star rating with the review count and its breakdown by star.

How to use it

Fetch one product from shop.tsukumo.co.jp, the Japanese PC-parts and electronics shop, by its thirteen-digit product number (e.g. '0730143315289') or a full product URL. The number is the product's barcode and its leading zero is significant, so keep it as text. Returns name, maker and maker_id, price with price_text and currency, availability and item_condition, stock_message, delivery_message, purchase_limit, badges, release_date (ISO, sometimes only year-month) with the raw release_date_text, summary, highlights, description and notes, image/images, breadcrumbs with category and category_id (the category filter of the search endpoint), specs, extended_specs (the manufacturer's own table, present only where the shop publishes one), rating, review_count, rating_breakdown keyed by star and review_url. Prices are in JPY and tax-included. The review bodies are on the products/reviews endpoint.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — TSUKUMO product number or a full product URL (examples: "0730143315289", "https://shop.tsukumo.co.jp/goods/0730143315289/")

Response

• @type string (default: "TsukumoProduct")
• id string required
• url string required
• name string nullable
• maker string nullable
• maker_id string nullable
• price number nullable
• currency string (default: "JPY")
• price_text string nullable
• points integer nullable
• customize_url string nullable
• availability string nullable
• item_condition string nullable
• stock_message string nullable
• delivery_message string nullable
• purchase_limit string nullable
• badges array (default: [])
• release_date string nullable
• release_date_text string nullable
• summary string nullable
• highlights string nullable
• description string nullable
• notes string nullable
• image string nullable
• images array (default: [])
• breadcrumbs array (default: [])
• category string nullable
• category_id string nullable
• specs object (default: {})
  • * string
• extended_specs object (default: {})
  • * string
• rating number nullable
• review_count integer nullable
• rating_breakdown object (default: {})
  • * integer
• review_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 number but no such product on shop.tsukumo.co.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.