Chewy Product Reviews API

Endpoint facts

Method

GET

API path

/chewy/product-reviews

Auth

apiKey

Credits

2 credits/request

Platform

Chewy

Response schema

#/definitions/chewy.reviewsResponseDoc

Overview

Returns one page of a Chewy product's customer reviews -- rating, title, body, author, submission date, helpful count, incentivized flag, and contributor badge -- with sorting and positive/negative filtering. chewy_product embeds only the first 20 reviews with no way to page past them; this endpoint reaches the whole set (products routinely carry thousands). id is the numeric id from any chewy.com PDP URL, and reviews are shared across a product's variants, so any variant's id returns the same set. total is the count for the current filter, so it drops when filter is applied, while rating_count stays the product's overall rating tally. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

2 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- `total` is the review count **for the current filter**, so it drops when `filter` is applied. `rating_count` stays the product's overall rating tally and does not move with the filter. - `has_next_page` reports whether more reviews follow the current page. - `reviews[].photo_urls` carries any customer-submitted photos on the review. Combine with `sort=PHOTOS` to surface photo reviews first. - `part_number` is the parent product's part number, which may differ from the `id` you passed (that is the variant's own id). - A page past the end returns an empty `reviews` array rather than an error. - An id Chewy does not recognize returns a `404`; a non-numeric id, an out-of-range `limit`, or an invalid `sort`/`filter` returns a `400`. Example response: ```json { "code": 200, "msg": "OK", "data": { "part_number": "67742", "total": 9696, "page": 1, "page_size": 20, "count": 20, "has_next_page": true, "rating": 4.4, "rating_count": 22965, "reviews": [ { "id": "…", "title": "Stormie approved!", "text": "My dog stopped itching within two weeks…", "rating": 5, "submitted_by": "vscarberry", "submitted_at": "2026-08-20T14:02:11Z", "helpful_count": 12 } ], "source_url": "https://www.chewy.com/api/pdp/graphql", "fetched_at": "2026-09-07T03:00:00Z" } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related