/rakuten/items/reviews

POST /api/rakuten/items/reviews

Price: 10 credits

Get Rakuten Ichiba item reviews by shop_code/item_code (or item URL): rating, title, text, author, posted/ordered date, helpful count, purpose tags, SKU info, review images/videos and shop replies.

How to use it

Get user reviews of a Rakuten Ichiba (楽天市場) item by shop_code/item_code (e.g. 'sawaicoffee-tea/ac-sale-1960') or a full item URL. Returns rating (1-5), title, text, author (nickname, sex, age_range), posted_date, ordered_date, helpful_count, purpose_tags, sku_info, review images/media and the shop's reply when present.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• item string required — Rakuten Ichiba item as shop_code/item_code or a full item URL (examples: "sawaicoffee-tea/ac-sale-1960", "https://item.rakuten.co.jp/sawaicoffee-tea/ac-sale-1960/"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "RakutenItemReview")
• id string required
• rating integer nullable
• text string nullable
• author string nullable
• author_sex string nullable
• author_age_range integer nullable
• posted_date string nullable
• ordered_date string nullable
• helpful_count integer nullable
• purpose_tags array (default: [])
• sku_info string nullable
• images array (default: [])
• media array (default: [])
  • @type string (default: "RakutenItemReviewMedia")
  • url string required
  • thumbnail string nullable
  • type string nullable
• shop_reply string nullable
• shop_reply_date 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 — Item not found (well-formed shop_code/item_code but the item does not exist) 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.