patagonia.com APIpatagonia.com ↗
Access Patagonia's product catalog, customer reviews, store locator, and Worn Wear used gear listings via a single structured API with 6 endpoints.
curl -X GET 'https://api.parse.bot/scraper/21a6a97f-f1d8-47f8-a022-981ba58f1cd1/search_products?sz=3&query=backpack&start=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for products by keyword on Patagonia.com. Returns paginated results with product name, price, brand, and category.
| Param | Type | Description |
|---|---|---|
| sz | integer | Number of results per page. |
| queryrequired | string | Search query keyword (e.g. 'backpack', 'jacket') |
| start | integer | Offset for pagination (increments by sz value each page). |
{
"type": "object",
"fields": {
"total": "integer count of products returned in this page",
"has_next": "boolean indicating if more results are available",
"products": "array of product objects with pid, name, price, brand, category, variant",
"next_start": "integer offset for next page, or null if no more results"
},
"sample": {
"data": {
"total": 3,
"has_next": true,
"products": [
{
"pid": "49260",
"name": "Black Hole® Micro MLC® 22L",
"brand": "Patagonia",
"price": 155,
"variant": null,
"category": "Bags"
}
],
"next_start": 3
},
"status": "success"
}
}About the patagonia.com API
This API covers 6 endpoints across Patagonia.com, giving developers structured access to product search, category browsing, detailed product specs, customer reviews sourced from Yotpo, store and authorized-dealer locations, and the Worn Wear used-gear inventory. The get_product_details endpoint returns color-mapped pricing, image arrays, variant attributes, materials, and fit descriptions by product ID — data that would otherwise require multiple page loads.
Product Search and Category Browsing
The search_products endpoint accepts a query string and returns a paginated array of product objects, each carrying a pid, name, price, brand, category, and variant. Pagination is controlled with start (offset) and sz (results per page); the response includes has_next and next_start so you can walk through large result sets without guessing offsets. The get_category_products endpoint works identically but scopes results to a category_id slug such as mens-jackets-vests or womens-fleece.
Product Details and Reviews
get_product_details takes a pid and returns the full product record: a price object keyed by color code (each with sale and list prices), a variants array listing available colors and sizes, an images object keyed by color code, and string fields for materials, fit, description, and style_number. Specs are returned as an array of {title, content} objects. Customer reviews come from the get_product_reviews endpoint, which wraps Yotpo data: each review object includes id, score, content, title, createdAt, and reviewer info. The bottomline object summarizes totalReview, averageScore, and a starDistribution breakdown. Pagination uses page and per_page parameters.
Store Locator and Worn Wear
The find_stores endpoint accepts lat, lng, and an optional dist radius in miles, returning an array of store objects with name, address, city, state, zip, phone, distance, and hours. Results include both Patagonia-owned stores and authorized dealers. The get_worn_wear_products endpoint takes no inputs and returns the full current inventory from the Worn Wear used and refurbished store — each product object includes title, handle, body_html, vendor, tags, variants (with price and condition), and images.
- Build a price-tracking tool that monitors sale vs. list price changes across color variants using
get_product_details. - Aggregate customer sentiment by pulling
averageScoreandstarDistributionfromget_product_reviewsacross multiple products. - Create a Worn Wear deal finder that surfaces used Patagonia gear by condition and price from
get_worn_wear_products. - Power a store-finder feature in an outdoor activity app using
find_storeswith user coordinates. - Index Patagonia's full catalog by iterating over category slugs with
get_category_productsand paginating vianext_start. - Compare materials and specs across jackets by collecting the
specsandmaterialsfields fromget_product_detailsfor multiplepidvalues. - Notify users when specific sizes reappear in stock by polling
variantsavailability inget_product_details.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Patagonia have an official developer API?+
What does `get_product_details` return beyond basic pricing?+
price object keyed by color code (each entry has separate sale and list prices), an images object also keyed by color code, a variants array with all available color and size combinations, and string fields for fit, materials, description, and style_number. Specs come back as an array of {title, content} objects.Does the API expose wishlist, cart, or account data?+
How does pagination work across search and category endpoints?+
search_products and get_category_products use start (an integer offset) and sz (results per page). Each response includes has_next (boolean) and next_start (integer or null). To get the second page, pass the next_start value from the previous response as the new start.