Chewy Product Q&A API

Endpoint facts

Method

GET

API path

/chewy/product-questions

Auth

apiKey

Credits

2 credits/request

Platform

Chewy

Response schema

#/definitions/chewy.questionsResponseDoc

Overview

Returns one page of a Chewy product's customer questions, each with its answers (text, author, date, staff flag, helpful count). chewy_product embeds only the first 20 questions with no way to page past them; this endpoint reaches the whole set. id is the numeric id from any chewy.com PDP URL, and questions are shared across a product's variants, so any variant's id returns the same set. Each question reports answers_total alongside its answers array, so a caller can tell when answers were truncated by answer_limit. Chewy offers no sort or filter on questions, so this endpoint deliberately exposes paging only. 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

- Each question reports `answers_total` alongside its `answers` array, so a caller can tell when answers were truncated by `answer_limit`. - Chewy offers no sort or filter on questions, so this endpoint exposes paging only. - A question carries no author or date of its own -- those exist on answers only, which is why `questions[].answers[]` has `submitted_by`/`submitted_at` and the question itself does not. - A page past the end returns an empty `questions` array with `has_next_page: false`. - An id Chewy does not recognize returns a `404`; a non-numeric id or an out-of-range `limit`/`answer_limit` returns a `400`. Example response: ```json { "code": 200, "msg": "OK", "data": { "part_number": "67742", "total": 142, "page": 1, "page_size": 20, "count": 20, "has_next_page": true, "questions": [ { "id": "…", "text": "What is the difference between small breed and adult?", "answers_total": 3, "answers": [ { "text": "Small breed has smaller kibble size and more calories.", "submitted_by": "Elizabeth", "submitted_at": "2026-07-02T18:41:00Z", "helpful_count": 1 } ] } ], "source_url": "https://www.chewy.com/api/pdp/graphql", "fetched_at": "2026-09-07T04: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