Chewy API

No. Chewy does not offer a public API for product, price or rating data. It runs an affiliate and creator program for links and commissions, which is not a product data API. The Scavio Chewy API fills that gap with 2 POST endpoints that return chewy.com data as structured JSON: search and product detail.

It is a REST API that returns public Chewy product data as JSON: keyword search or category browse with one-time, Autoship and first-Autoship prices, ratings and stock, and product detail with MAP fields, star distribution, specifications and every variant.

10 credits per successful call, on both endpoints. Errors such as an unknown product (404) or a temporary outage (502) are not charged. New accounts get 50 free credits on signup, one time, with no card required, which covers 5 Chewy calls. Paid plans start at $30 per month for 7,000 credits, which is 700 Chewy calls.

Yes. Every search result and product carries autoship_price and autoship_discount_pct, the recurring Autoship price, plus first_autoship_price, first_autoship_discount_pct and first_autoship_max_savings for the first Autoship order. In our capture a Kseroo chew toy was $17.99 one-time and $17.09 on Autoship, 5% off. A field is null when Chewy shows no such price: deal items can have no Autoship price even when autoship_allowed is true.

It is the price of a customer's first Autoship order, which Chewy discounts more than the recurring Autoship price. first_autoship_max_savings is the cap on that discount in dollars. All three fields are null on items where Chewy shows no first-order offer.

Yes. map_price is the minimum advertised price and map_enforced says whether it is enforced on the item. Read them from the product endpoint: the captured search had them null on every row, while the product call for the KONG Classic, Large returned map_price 13.96 and map_enforced false.

It returns ratings, not review text. Search has rating and rating_count. Product adds review_count, rating_distribution with the count and percent at each star, and attribute_scores. The KONG Classic had a 4.5668 rating from 8,508 ratings, 6,829 of them five stars, and 3,970 reviews.

Chewy sends some broad queries straight to a category page instead of running a search, for example "dog food" lands on category 332, Dog Food. The response then has redirect with that category's category_id, name and url, and products are that category's listing. A specific query such as "kong classic dog toy" stays a search and redirect is null.

No. Sponsored listings are removed so products holds organic results only, and sponsored_removed says how many were taken out. Our capture removed 9 alongside 36 organic results.

Yes. Pass category_id instead of query: the number at the end of a chewy.com /b/ URL (332 is Dog Food), or that URL. Sort by relevance, bestselling, newest, price_low, price_high, rating or most_reviewed, 36 results per page for up to 100 pages.

Yes. The product endpoint returns variants[], every size or flavor with its own product_id, price, Autoship price, per-unit price and stock, with selected marking the one you asked for. The KONG Classic came back in 6 sizes.

No. Chewy sells online and has no stores, so the API takes no store or ZIP parameter. in_stock is Chewy's online availability.

No. Pharmacy is out of scope. Search and product flag prescription and vet-diet items with is_prescription and is_vet_diet, and that is all.

Each call costs 10 credits. There are 2 endpoints, search and product, with no review text, no stores and no pharmacy. Prices are in US dollars, for chewy.com only. A broad query can come back as a category page, reported in redirect. A call typically takes a few seconds.

Every request fetches live from Chewy at the moment you call it, and nothing is cached. Each response carries fetched_at, the time the data was retrieved.

Scavio returns publicly available Chewy product data and does not access accounts or order history. You remain responsible for how you use the data, including compliance with Chewy's terms. Talk to your own counsel for your specific use case.