/johnlewis/products/reviews

POST /api/johnlewis/products/reviews

Price: 5 credits

Get customer reviews for a John Lewis product by product id (or product URL): title, text, rating, date, reviewer name and location, helpful/unhelpful counts, verification tags, photos and per-review subratings (e.g. Quality, Value).

How to use it

Fetch customer reviews for a John Lewis product by numeric product id or a product URL. Returns up to `count` reviews, each with id, title, text, rating (1-5) and rating_label, created_at (unix ms), reviewer {user_name, location}, helpful_count, unhelpful_count, tags (e.g. isVerifiedBuyer, isVerifiedReviewer, isPartner), media (photo URLs) and subratings [{name, value, value_label}] for aspect ratings like Quality and Value. This is John Lewis's own review system. A product with no reviews (or a nonexistent product) returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — John Lewis product id or a product URL containing it (examples: "3310302", "https://www.johnlewis.com/x/p3310302"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "JohnlewisReview")
• id string required
• text string nullable
• rating number nullable
• rating_label string nullable
• created_at integer nullable
• reviewer object nullable
  • @type string (default: "JohnlewisReviewer")
  • user_name string nullable
  • location string nullable
• helpful_count integer nullable
• unhelpful_count integer nullable
• tags array (default: [])
• media array (default: [])
• subratings array (default: [])
  • @type string (default: "JohnlewisReviewSubrating")
  • name string required
  • value number nullable
  • value_label 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 — The entity was not found, or a precondition failed 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.