backcountry.com APIbackcountry.com ↗
Access Backcountry.com product listings, pricing, stock status, ratings, and brand data via 4 structured JSON endpoints. Search, browse by category, or get product details.
curl -X GET 'https://api.parse.bot/scraper/0bcf4d02-d146-49f1-b476-86c7221c0796/search_products?sort=Featured&limit=3&query=backpack' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for products by keyword query. Returns paginated product listings with pricing, ratings, colors, and stock status.
| Param | Type | Description |
|---|---|---|
| sort | string | Sort order for results. |
| after | string | Pagination cursor from page_info.pages[].cursor in a previous response. Pass to fetch the corresponding page. |
| limit | integer | Max results to return per page. |
| queryrequired | string | Search keyword (e.g. 'jacket', 'backpack', 'hiking shoes'). |
{
"type": "object",
"fields": {
"total": "integer total number of matching products",
"products": "array of product objects with id, name, url, stockStatus, brand, aggregates, flags, reviewAggregates, and colors",
"page_info": "object with hasNextPage boolean and pages array of cursor values for pagination"
},
"sample": {
"data": {
"total": 875,
"products": [
{
"id": "TNFZB13",
"url": "/the-north-face-recon-backpack",
"name": "Recon 30L Backpack",
"brand": {
"name": "The North Face"
},
"flags": {
"isExclusive": false,
"isNewArrival": false,
"isPastSeason": true,
"isGearheadPick": false
},
"colors": [
{
"name": "Timber Tan",
"colorId": "TIMTAN",
"pliImage": "/images/items/large/TNF/TNFZB13/TIMTAN.jpg",
"tileImage": "/images/items/160/TNF/TNFZB13/TIMTAN.jpg"
}
],
"aggregates": {
"maxDiscount": 0,
"minDiscount": 0,
"totalColors": 6,
"maxListPrice": 125,
"maxSalePrice": 125,
"minListPrice": 125,
"minSalePrice": 125,
"totalVariations": 6,
"variationsOnSale": 0
},
"stockStatus": "IN_STOCK",
"reviewAggregates": {
"totalReviews": 1190,
"averageRating": 4.5
}
}
],
"page_info": {
"pages": [
{
"value": 2,
"cursor": "Mg=="
}
],
"hasNextPage": true
}
},
"status": "success"
}
}About the backcountry.com API
The Backcountry.com API provides 4 endpoints for querying outdoor gear listings, covering search, category browsing, product details, and brand enumeration. The search_products endpoint accepts a keyword query and returns paginated results with pricing aggregates, stock status, review scores, and available colors — covering everything from jackets to hiking boots across Backcountry's full catalog.
Endpoints and Data Coverage
The API exposes four endpoints. search_products accepts a query string (e.g. 'backpack' or 'hiking shoes') plus optional sort, limit, and cursor-based after parameters, returning an array of product objects with fields including id, name, url, stockStatus, brand, aggregates (pricing), flags, reviewAggregates, and colors. The total field gives the full result count and page_info provides a hasNextPage boolean and a pages array of cursor values for stepping through results.
Category and Product Detail Lookups
get_category_products works identically to search but scoped to a category slug such as 'bc-ski', 'bc-climb', 'bc-hike-camp', or 'bc-bike'. The same pagination model applies. get_product_details takes a product slug (the URL path segment from the url field in search or category results) and returns the full product object — same field shape — alongside a reviews array. Note that the reviews array is currently empty; review text is not returned by this endpoint even though reviewAggregates (summary scores) are present on the product object.
Brand Data
list_all_brands requires no inputs and returns a brands array where each entry contains a name string and a product_count integer, sorted descending by count. The total field reports how many distinct brands were found. This endpoint is useful for building brand filters or understanding catalog distribution across outdoor gear manufacturers sold on Backcountry.com.
- Build a price-tracking tool that monitors
aggregatespricing fields for specific gear items usingget_product_details. - Aggregate in-stock status across a category with
get_category_productsandstockStatusto surface available gear during peak seasons. - Populate a gear comparison app by fetching product details for multiple slugs and comparing
reviewAggregatesscores and color options. - Enumerate the brand catalog with
list_all_brandsto build a brand-indexed gear directory with product counts. - Drive a keyword-based gear recommendation engine using
search_productswith outdoor activity terms. - Extract category-level product data from
bc-skiorbc-snowboardslugs to analyze winter sports inventory. - Build an affiliate product feed by paginating through
get_category_productsresults and collectingurland pricing fields.
| 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 Backcountry.com have an official developer API?+
What does `get_product_details` return, and are full customer reviews included?+
id, name, stockStatus, brand, aggregates (pricing), flags, reviewAggregates (summary scores like average rating and count), and colors. The reviews array is currently empty — individual review text and metadata are not returned by this endpoint. You can fork the API on Parse and revise it to add a dedicated reviews endpoint if you need review-level detail.How does pagination work across `search_products` and `get_category_products`?+
page_info object containing a hasNextPage boolean and a pages array of cursor objects. Pass the desired cursor value to the after parameter on your next request to fetch that page. The total field on each response gives the full matching product count regardless of the current page.Are sale prices, discount percentages, or promotional flags returned?+
aggregates field on each product object contains pricing data, and a flags field is included on every product. The exact sub-fields within aggregates (such as original vs. sale price breakdowns) are present where the source exposes them. Computed discount percentages are not a separate dedicated field. You can fork the API on Parse and revise it to derive and surface discount calculations from the pricing fields.Which category slugs are supported by `get_category_products`?+
bc-mens-clothing, bc-womens-clothing, bc-hike-camp, bc-ski, bc-climb, bc-kids, bc-snowboard, and bc-bike. Sub-category slugs beyond these top-level categories are not currently listed. You can fork the API on Parse and revise it to support additional category IDs as needed.