Chewy Warehouse Inventory API

Endpoint facts

Method

GET

API path

/chewy/inventory

Auth

apiKey

Credits

3 credits/request

Platform

Chewy

Response schema

#/definitions/chewy.inventoryResponseDoc

Overview

Returns Chewy's live warehouse inventory position for up to 20 products in one call, keyed by part number: the availability status, total units on hand, units inbound/in progress, units already reserved against unshipped orders, and the quantity actually available to the storefront. This is the only Chewy surface that carries real quantities -- every other endpoint in this family reports stock as a single boolean, so "36 units left" and "84,386 units left" are indistinguishable there. Quantities are live and move between calls. Part numbers Chewy does not return inventory for are reported in not_found; if none 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

3 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[].status` is Chewy's own availability enum: `AVAILABLE`, `OUT_OF_STOCK`, `OUTSIDE_TNT` (stocked, but not deliverable to the requested destination inside the promised transit window). - `items[].quantity_on_hand` is total units physically in Chewy's warehouses; `items[].quantity_available_to_site` is what the storefront may actually sell, and is typically far lower. The latter is the figure that governs whether a product reads as in stock. - `items[].quantity_in_progress` is inbound units not yet on hand; `items[].quantity_reserved` is units already committed to unshipped orders. - Quantities are live and change between calls. - Part numbers Chewy returns no inventory for are listed in `not_found` rather than reported as zero stock, since zero would be a materially wrong answer. If none of the requested part numbers resolve, the response is a `404`. Example response: ```json { "code": 200, "msg": "OK", "data": { "count": 2, "items": [ { "part_number": "101143", "status": "AVAILABLE", "quantity_on_hand": 84383, "quantity_in_progress": 5493, "quantity_available_to_site": 11410, "available_date": "2026-09-06T14:25:54.247346Z" }, { "part_number": "4238414", "status": "AVAILABLE", "quantity_on_hand": 36, "quantity_available_to_site": 18 } ], "source_url": "https://www.chewy.com/api/item/v1/item/101143,4238414", "fetched_at": "2026-09-06T09: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