Chewy Product Attributes API

Endpoint facts

Method

GET

API path

/chewy/item-attributes

Auth

apiKey

Credits

4 credits/request

Platform

Chewy

Response schema

#/definitions/chewy.itemAttributesResponseDoc

Overview

Returns Chewy's own specification table for up to 20 products in one call, keyed by part number -- the structured attribute list (lifestage, pet type, product type, material, made-in country, packaging type, flavor, defining size, plus long-form key-benefits and cautions copy), together with the handling and compliance flags that govern how an item ships (pharmaceutical, prescription vet-diet, frozen, refrigerated, single-tablet, gift card), its bundle structure and component SKUs, its autoship eligibility/discount and preset reorder cadence, its merchandising classification path, and the numeric category group ids it belongs to (each usable directly as chewy_category's group_id). This complements rather than repeats chewy_products and chewy_product: price, rating, images, reviews, and descriptions stay on those endpoints, and the attribute table is not available from either. Use the group parameter to return a single attribute group. Part numbers Chewy does not recognize are reported in not_found; if none of them resolve the response is a 404. 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

4 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

- `items[].attributes[]` is the structured specification table. Each entry has an `identifier` (Chewy's own attribute key, e.g. `LitterMaterial`, `Lifestage`, `MadeIn`, `KeyBenefits`), its `group` and `usage`, and one or more `values`. An attribute can carry several values -- `Lifestage` is commonly `["All Lifestages", "Adult"]`. A typical SKU returns 25-35 attributes. - The handling and compliance flags -- `is_pharmaceutical`, `is_vet_diet`, `is_frozen`, `is_refrigerated`, `is_single_tablet`, `is_gift_card` -- govern how an item ships and whether it needs veterinary authorization. `is_vet_diet` is `true` for prescription-diet foods. These are omitted when false. - `items[].category_group_ids` is the list of numeric category group ids the item belongs to. Each is directly usable as `/chewy/category`'s `group_id`, so this is a reverse index from a SKU back to every category listing that contains it. - `items[].merch_class_identifiers` is Chewy's merchandising classification path, e.g. `["f2-cat-consumables", "f2-cat-consumables-litter", ...]`, ordered broad to narrow. - `items[].preset_frequency` is the item's default autoship cadence, e.g. `{"unit":"WEEK","value":5}`. `unit` is one of `DAY`, `WEEK`, `MONTH`. - Bundle products carry `is_bundle` plus `bundle_items[]` listing the component SKUs; `is_bundle_multi_sku` and `is_bundle_same_sku` distinguish the two bundle kinds. - Part numbers Chewy does not recognize are returned in `not_found` rather than as null entries -- upstream silently drops them. If none of the requested part numbers resolve, the response is a `404`. - Per-product promotion/deal detail is deliberately not exposed here; it requires customer context upstream and is unavailable to an anonymous caller. Example response: ```json {"code":200,"msg":"OK","data":{"count":1,"not_found":["99999999999"],"items":[{"part_number":"52448","entry_id":"37591","name":"Lavender Scented Clumping Corn Cat Litter, 28-lb bag","brand":"World's Best","gtin":"322591001700","is_published":true,"is_autoship_allowed":true,"autoship_discount_pct":5,"preset_frequency":{"unit":"WEEK","value":5},"merch_class_identifiers":["f2-cat-consumables","f2-cat-consumables-litter"],"category_group_ids":["10016","2731","411"],"attributes":[{"identifier":"Size","name":"Size","group":"DEFINING","usage":"DEFINING","displayable":true,"values":[{"id":1,"value":"28-lb bag"}]},{"identifier":"LitterMaterial","name":"Litter Material","group":"STANDARD","usage":"DESCRIPTIVE","displayable":true,"values":[{"id":2,"value":"Corn"}]}]}],"source_url":"https://www.chewy.com/api/subscriptions/graphql","fetched_at":"2026-09-06T10: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