/revolve/products/reviews

POST /api/revolve/products/reviews

Price: 10 credits

Get customer reviews for a REVOLVE product: rating, title, text, author, submission date, verified-buyer and incentivized flags, sentiment score, reviewer country and language, helpful votes, discussed topics, photos, and the fit answers REVOLVE collects from reviewers (how the item sizes, the reviewer's build and height, perceived quality and whether they recommend it).

How to use it

Fetch reviews for one REVOLVE product by product code or product URL. Each review has id, rating, review_title, text, created_at (unix seconds), author, is_verified_buyer, is_incentivized, sentiment, country, language, vote_up_count, vote_down_count, topics, images and fit — the fit block is the useful part for apparel: sizing (runs small / true to size / runs large), curves, height, quality and is_recommended. Use the REVOLVE review summary endpoint for the aggregate picture without downloading every review.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — REVOLVE product code or a product page URL containing it (examples: "ASTR-WD190", "https://www.revolve.com/astr-the-label-blythe-dress/dp/ASTR-WD190/"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• sort string — Review ordering (default: "smart"; one of: "smart", "date", "rating", "votes_up", "images")
• direction string — Ordering direction (default: "desc"; one of: "desc", "asc")

Response

• @type string (default: "RevolveReview")
• id string required
• rating integer nullable
• review_title string nullable
• text string nullable
• created_at integer nullable
• author string nullable
• is_verified_buyer boolean nullable
• is_incentivized boolean nullable
• incentive_type string nullable
• sentiment number nullable
• country string nullable
• language string nullable
• vote_up_count integer nullable
• vote_down_count integer nullable
• reviewed_product string nullable
• reviewed_product_image string nullable
• topics array (default: [])
  • @type string (default: "RevolveReviewTopicMention")
  • name string required
  • sentence string nullable
• images array (default: [])
• fit object nullable
  • @type string (default: "RevolveReviewFit")
  • sizing string nullable
  • curves string nullable
  • height string nullable
  • quality string nullable
  • is_recommended boolean 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 but nonexistent product code) 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.