/misumi/products/reviews

POST /api/misumi/products/reviews

Price: 1 credit

List customer reviews of a MISUMI (ミスミ) series: star rating, title, review text, post date, how many people found it helpful, and the manufacturer's public reply where one was given. Can be filtered to one star rating and ordered by rating, recency or helpfulness.

How to use it

List reviews of one MISUMI series. Accepts a series code, any part number (型番) of the series, or a product URL — reviews are held at series level, not per part number. `created_at` is a unix timestamp in seconds (the source publishes the date only, so it points at midnight UTC) and `created_date` keeps the original YYYY/MM/DD string. `reply` is MISUMI's own answer to the reviewer. A product with no reviews returns an empty list, not an error. The average rating and the star histogram are on misumi/products.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — MISUMI series code (e.g. '110302280360'), a part number (型番) belonging to the series, or a full product URL (examples: "110302280360", "BOX-CBE3-10"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• rating integer nullable — Only reviews that gave exactly this many stars (min: 1; max: 5)
• sort string — Result ordering (default: "rating_desc"; one of: "rating_desc", "most_helpful", "newest", "rating_asc")

Response

• @type string (default: "MisumiReview")
• id string required
• series_id string required
• series_url string required
• review_title string nullable
• text string nullable
• rating number nullable
• helpful_count integer nullable
• created_at integer nullable
• created_date string nullable
• reply 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 — Series not found (well-formed series code or part number, but no such product on MISUMI) 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.