POST /api/tsukumo/products/reviews
Price: 5 credits
Get the customer reviews posted on a TSUKUMO (ツクモ) product: the reviewer, star rating, headline, full body, posting time and how many shoppers found the review helpful, optionally narrowed to one star level.
Reviews of one shop.tsukumo.co.jp product, addressed by its thirteen-digit product number (e.g. '0730143315289') or a full product URL. Set rating to read only the one-star or only the five-star reviews. Each review carries id, product_id, author with author_id and author_url, rating (1-5), review_title, text, created_at (unix seconds) with the raw created_at_text, and helpful_count. Japanese shoppers write long, technical reviews here, so text is usually several paragraphs. A product nobody has reviewed returns an empty list; the rating average, the review total and the breakdown by star are on the products endpoint.
access-token string requiredtimeout 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/")count integer required — Max number of reviews to return (min: 1)rating integer nullable — Keep only the reviews that awarded this many stars (min: 1; max: 5)@type string (default: "TsukumoProductReview")id string nullableproduct_id string requiredauthor string nullableauthor_id string nullableauthor_url string nullablerating number nullablereview_title string nullabletext string nullablecreated_at integer nullablecreated_at_text string nullablehelpful_count integer nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.