/monotaro/products/reviews

POST /api/monotaro/products/reviews

Price: 10 credits

List MonotaRO (モノタロウ) product reviews: star rating, review text, the reviewing company or customer name, the industrial use case the reviewer describes (用途), the exact SKU reviewed, publication date and helpful-vote count. Supports ordering and filtering by star rating.

How to use it

Read MonotaRO (モノタロウ) product reviews written by Japanese trade and industrial buyers. Reviews belong to a product family, so pass a product-group code (商品コード), any order code of the family, or a product URL — the two code spaces overlap, so set `code_type` when you pass bare digits, or pass the URL. `usage` is the reviewer's stated application (e.g. 'car maintenance', 'electrical work') — a signal you rarely get on consumer marketplaces. `author` is the reviewing company (often a named 株式会社) or the customer's display name, when they chose to show it — a direct read on which businesses buy the part. `order_code` names the exact SKU reviewed when the reviewer selected one. `created_at` is a unix timestamp in seconds. A product with no reviews returns an empty list, not an error.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — MonotaRO product-group code (商品コード, e.g. '00005036'), any order code (注文コード) belonging to the family, or a full product URL (examples: "00005036", "https://www.monotaro.com/g/00005036/", "02197517"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• rating integer nullable — Only reviews with exactly this star rating (min: 1; max: 5)
• sort string — Review ordering (default: "recommended"; one of: "recommended", "newest", "most_helpful")
• code_type string — Which code space `product` belongs to when it is passed as bare digits. The two code spaces overlap — the same eight digits can name one SKU and a different whole product family. Ignored when `product` is a URL (default: "order_code"; one of: "order_code", "product_code")

Response

• @type string (default: "MonotaroReview")
• id string required
• product_code string required
• product_url string required
• author string nullable
• rating number nullable
• text string nullable
• usage string nullable
• order_code string nullable
• order_code_url string nullable
• created_at integer nullable
• created_date string nullable
• helpful_count 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 code but no such product on MonotaRO) 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.