Chewy Search Facets API

Endpoint facts

Method

GET

API path

/chewy/facets

Auth

apiKey

Credits

2 credits/request

Platform

Chewy

Response schema

#/definitions/chewy.facetsResponseDoc

Overview

Returns the full set of refinement options (facets) a Chewy category or keyword search can be narrowed by -- brand, sub-category, lifestage, food form, breed size, special diet, health feature, flavor, ingredient, packaging type, price band, customer rating, and whichever other dimensions that listing exposes -- with each option's product count. No products are returned, so this is a much smaller call than chewy_category/chewy_search when only the option set is wanted. The Brand dimension is effectively Chewy's brand directory for the requested listing: each brand option carries its product count and, where Chewy publishes one, its own chewy.com/brands/<slug>-<id> landing-page slug in seo_hvf_slug. Exactly one of group_id or q is required. Every facets[].value paired with one of that facet's options[].value is a ready-to-use filter key:value pair for this endpoint, chewy_category, and chewy_search alike; passing filter here narrows the listing first, so the returned counts describe the already-narrowed result set. A group_id Chewy does not recognize returns a 404 rather than an empty option set. 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

- The `Brand` dimension (`facets[].value` == `"brand_facet"`) is effectively Chewy's brand directory for the requested listing -- every brand carrying at least one matching product, with its product count. A top-level department returns thousands of brands (e.g. `group_id=288`, Dog, returns over 3,000). - `options[].seo_hvf_slug`, present on brand options Chewy publishes a landing page for, is that brand's own `chewy.com/brands/<slug>-<id>` page slug (e.g. `acana-dry-dog-food`) -- Chewy's canonical brand name for URL purposes. It is scoped to the listing being refined (ACANA is `acana-dry-dog-food` under `group_id=294` but `acana-dog-food` under its parent `332`), and Chewy publishes one for far fewer brands at department level than at sub-category level. `options[].url_slug` is the equivalent for a sub-category option. - `options[].id` is Chewy's own internal id for the option, omitted where upstream has none (the synthetic Category, Price and Customer Rating dimensions). - Every `facets[].value` paired with one of that facet's `options[].value` is a ready-to-use `filter` `key:value` pair for this endpoint, `/chewy/category`, and `/chewy/search` alike. When `facets[].value` is `"categoryId"`, each `options[].value` is also a ready-to-use `group_id`. - `total` is the number of products the requested listing matches (after any `filter` is applied). `count` is the number of facet dimensions returned. - A `group_id` Chewy does not recognize returns a `404` rather than an empty option set. A `q` that matches nothing returns `200` with an empty `facets` array and `total` of `0`. - The facet dimensions vary by listing -- a food category exposes flavor/ingredient/special-diet dimensions a toy category does not. Example response: ```json {"code":200,"msg":"OK","data":{"group_id":"294","total":2208,"count":2,"facets":[{"name":"Category","value":"categoryId","count":1,"options":[{"name":"Health Condition","display_label":"Health Condition Dry Dog Food","value":"132958","url_slug":"science-backed-formulas","product_count":752}]},{"name":"Brand","value":"brand_facet","count":2,"options":[{"id":"507405","name":"ACANA","display_label":"ACANA","value":"ACANA","seo_hvf_slug":"acana-dry-dog-food","product_count":93},{"id":"330132","name":"Purina Pro Plan","display_label":"Purina Pro Plan","value":"Purina Pro Plan","seo_hvf_slug":"Purina-Pro-Plan-Dry-Dog-Food","product_count":142}]}],"source_url":"https://www.chewy.com/plp/api/facets?catalogId=1004&groupId=294","fetched_at":"2026-09-05T10: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