List Chewy's brand directory API

Endpoint facts

Method

GET

API path

/chewy/brands

Auth

apiKey

Credits

2 credits/request

Platform

Chewy

Response schema

#/definitions/chewy.brandsResponseDoc

Overview

Returns one page of Chewy's full brand directory -- roughly 7,600 brands -- with each brand's id, name, Chewy's own written description, image, parent-catalog group, and its child brands where a brand umbrellas others (Purina lists 27). This is the whole catalog of brands, unlike chewy_facets, which only reports the brands present in one category's listing. Pass name to look up a single brand by exact name, case-insensitive; it is an exact match upstream, not a search, so "Purina" matches while "purina pro" does not. To filter products by a brand, pass the brand's NAME to chewy_category or chewy_search as filter=brand_facet:<name> -- facet_id is the join key onto chewy_facets' own option ids and is not accepted by the filter parameter. 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

- **To filter products by brand, pass the brand's `name`** to `/chewy/category` or `/chewy/search` as `filter=brand_facet:<name>` -- e.g. `filter=brand_facet:ACANA` returns 33 products on `group_id=294`. - `facet_id` is **not** accepted by that filter. It is the join key onto `/chewy/facets`' own `options[].id` for the same brand (ACANA is `id` 74 here and `facet_id` 507405, which is exactly the option id `/chewy/facets` reports). Passing `filter=brand_facet:507405` returns nothing. - `child_brand_ids` lists the ids of sub-brands under an umbrella brand. - `short_description` is omitted when it merely repeats the brand name, which upstream does for most entries. - Roughly a fifth of brands carry a `long_description`; the rest are name-only catalog entries. - A `name` that matches nothing, or a page past the end, returns an empty `brands` array rather than an error. - An out-of-range `limit` or `page` returns a `400`. Example response: ```json { "code": 200, "msg": "OK", "data": { "page": 1, "page_size": 100, "count": 100, "brands": [ { "id": "74", "name": "ACANA", "facet_id": "507405", "long_description": "ACANA pet foods are made with fresh regional ingredients…", "updated_at": "2026-09-06T06:30:47.112Z" } ], "source_url": "https://www.chewy.com/api/search/brands?catalogId=1004&count=100&from=0", "fetched_at": "2026-09-07T06: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