/revolve/products/reviews/summary

POST /api/revolve/products/reviews/summary

Price: 1 credit

Get the aggregate review picture for a REVOLVE product without downloading the reviews: average rating, review count, per-star breakdown, the fit consensus REVOLVE collects from reviewers (how the item sizes and its perceived quality), an AI-written summary paragraph, discussed topics with per-topic summaries and sentiment, quoted highlights, and where reviewers are shopping from.

How to use it

Cheap aggregate view of a REVOLVE product's reviews by product code or product URL. Returns one item with id, rating, review_count, rating_distribution (per-star counts), fit (sizing and quality consensus), summary, topics, topic_summaries (each with mention_count and sentiment), highlights and countries. Use the REVOLVE reviews endpoint when you need the individual review texts.

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)

Response

• @type string (default: "RevolveReviewSummary")
• id string required
• rating number nullable
• review_count integer nullable
• rating_distribution array (default: [])
  • @type string (default: "RevolveRatingBucket")
  • rating integer required
  • review_count integer nullable
• fit object nullable
  • @type string (default: "RevolveReviewFitSummary")
  • sizing string nullable
  • sizing_score number nullable
  • quality string nullable
  • quality_score number nullable
• summary string nullable
• topics array (default: [])
• topic_summaries array (default: [])
  • @type string (default: "RevolveReviewTopic")
  • name string required
  • display_name string nullable
  • summary string nullable
  • mention_count integer nullable
  • sentiment number nullable
• highlights array (default: [])
  • @type string (default: "RevolveReviewHighlight")
  • review_id string required
  • author string nullable
  • text string nullable
• countries array (default: [])
  • @type string (default: "RevolveReviewCountry")
  • code string required
  • name string nullable
  • review_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 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.