Luxury ready-to-wear and accessories pricing monitoring
Use Balenciaga endpoints to turn luxury ready-to-wear and accessories pricing monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Balenciaga's own public storefront into structured JSON — a full category taxonomy, keyword and category browsing through Balenciaga's own Search-ShowAjax listing fragment with live facet counts, full product detail sourced from each page's own schema.org markup, the complete color/size variation matrix, and the worldwide boutique locator by country. Normalized JSON, credential-free.
Browse Balenciaga's category tree, search with live facets, get full product detail with variants, and look up boutiques by country as structured JSON.
Endpoint families
6
Documented params
19
Examples
7
Live catalog snapshot
Active endpoints
7
Methods
GET
Required params
12
Schema refs
7
{
"platform": "Balenciaga",
"endpoint": "balenciaga-search",
"method": "GET",
"path": "/balenciaga/search",
"auth": "apiKey"
}Use cases
Browse Balenciaga's category tree, search with live facets, get full product detail with variants, and look up boutiques by country as structured JSON.
Use Balenciaga endpoints to turn luxury ready-to-wear and accessories pricing monitoring into repeatable API requests with documented inputs and JSON responses.
Use Balenciaga endpoints to turn category assortment and facet-driven merchandising research into repeatable API requests with documented inputs and JSON responses.
Use Balenciaga endpoints to turn boutique network and market-availability mapping into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Balenciaga endpoint catalog — 7 endpoints, 19 documented request parameters, and 7 published response schemas — the same catalog Docs and Playground run against.
7 documented Balenciaga endpoints, grouped into 6 request families — Product, Categories and Category, plus 3 more.
19 request parameters are documented across those Balenciaga endpoints, 12 of them required — the full input contract is public before you write any integration code.
7 of the 7 Balenciaga endpoints ship a recorded example response, and 7 carry a documented response schema — you can code against the real JSON before the first request.
Balenciaga endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
7 hosted MCP tools back the Balenciaga endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/balenciaga/product
/balenciaga/categories
/balenciaga/category
/balenciaga/search
/balenciaga/store-countries
/balenciaga/stores
Endpoint catalog
/balenciaga/searchSearches Balenciaga's storefront by keyword using the site's own product-grid fragment. q is required; sort accepts latest, price_ascending, or price_descending; page is one-based with 12 products per page; and filters accepts comma-separated exact field:value pairs from live facets. Repeat a field to OR multiple values within that facet. A genuine no-result query returns an empty products list.
Response notes
- Search uses the product-grid fragments fired by Balenciaga's own sort and load-more controls. - Search filters are passed to the same storefront facet parameters as the live UI; different facet fields are combined, and repeated values within one field are ORed upstream. - A genuine no-result query returns `count: 0` and `products: []`. - Product URLs in the response can be passed directly to `balenciaga-product`.
Sampled 14 Oct 2026: 12 items, 5 fields filled in every item, 1 not. name: “hourglass handbag xs” and 7 other values; url: balenciaga.com.
MCP tool balenciaga_search
/balenciaga/categoryReturns one Balenciaga category listing from the site's own Search-ShowAjax fragment. path comes from balenciaga-categories. sort accepts latest, price_ascending, or price_descending. filters is a comma-separated list of exact field:value pairs from the response's live facets; repeat a field to OR multiple values within that facet; omit it for an unfiltered listing.
Response notes
- The endpoint uses Balenciaga's own `Search-ShowAjax` HTML fragment and returns its live total and facet counts. - `sort` values map to the upstream values `NewIn`, `PriceAscending`, and `PriceDescending`. - Do not invent facet values; use a prior response's `facets` values.
Sampled 14 Oct 2026: 16 items, 5 fields filled in every item, 1 not. name: “le city bucket bag nano” and 9 other values; url: balenciaga.com.
MCP tool balenciaga_category
/balenciaga/categoriesLists Balenciaga's storefront categories with `count`, and for each its `id`, `name`, `department`, `path` and `url`. Each `path` is the value `balenciaga-category` accepts. The response reports `country` (`ZW`) and `language` (`en`).
Response notes
- The taxonomy is read from Balenciaga's own navigation links. - `country` is `ZW` and `language` is `en` for this first validated storefront contract.
Sampled 14 Oct 2026: 182 items, 5 fields filled in every item. name: “A New York Minute” and 124 other values; url: balenciaga.com.
MCP tool balenciaga_categories
/balenciaga/productReturns structured product detail from Balenciaga's product page, including schema.org name/SKU/price/availability, images, color variants, and visible product details. url must be a product URL returned by balenciaga-category or balenciaga-search.
Response notes
- The product page's schema.org JSON-LD supplies the canonical name, SKU, description, price, currency, availability, and images when present. - Visible color variants, product-detail bullets, dimensions, and product-care text are included when present. Each color variant includes a `url` for the site's live `Product-Variation` request, which can be passed to `balenciaga-product-variants`. - Unknown or malformed product URLs are rejected before the upstream request.
Sampled 14 Oct 2026: 13 of 13 fields returned with a value. name: “Women's Hourglass Avenue Top Handle Bag Small in Black”; url: balenciaga.com.
MCP tool balenciaga_product
/balenciaga/product/variantsReturns Balenciaga's live color/size variation matrix for a product, including variation ids, selection/sellability flags, care text, availability, and related product ids. url may be a product URL or a Product-Variation URL from balenciaga-product's colors[].url.
Sampled 14 Oct 2026: 2 items, 4 fields filled in every item. selected_value: “White Snow” and 1 other value; values: median 1 entry.
MCP tool balenciaga_product_variants
/balenciaga/storesReturns Balenciaga's public physical-store directory for one country, including addresses, coordinates, phone numbers, opening hours, and store-service flags. Use balenciaga-store-countries to discover the complete accepted country enum.
Sampled 14 Oct 2026: 31 items, 20 fields filled in every item. name: “Santa Clara - Westfield Valley Fair” and 30 other values; details_url: balenciaga.com.
MCP tool balenciaga_stores
/balenciaga/store-countriesLists the countries Balenciaga's store locator offers, each with a country `code` and `name`, plus a `count`. Each code is accepted by `balenciaga-stores`. The response also reports the storefront `country` and `language`.
Sampled 14 Oct 2026: 32 items, 2 fields filled in every item. name: “United Arab Emirates” and 31 other values.
MCP tool balenciaga_store_countries
Related APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
How to scrape Balenciaga
Crawlora's seven Balenciaga endpoints return category, search, product, variant, and store data as normalized JSON with one API key — category and search share the same product-grid and facet shape, since both read Balenciaga's own live listing fragments.
Call /balenciaga/categories for the full navigation/category taxonomy, each with a path usable directly on /balenciaga/category. Both /balenciaga/category and /balenciaga/search accept sort (latest, price_ascending, or price_descending), page, and a comma-separated filters list of exact field:value pairs — read the response's own live facets (e.g. akeneo_macroColor:BLACK) rather than inventing values, and repeat a field to OR multiple values within it.
Send q to /balenciaga/search for keyword search across the full catalogue, 12 products per page. total_results is Balenciaga's own true match count independent of the page size, and a genuine no-result query returns count: 0 with an empty products array.
Pass a product url from any search/category/store result to /balenciaga/product — its schema.org JSON-LD supplies name, SKU, description, price, currency, availability, and images, plus visible color variants, dimensions, and care text when present. Each color variant carries its own url for /balenciaga/product/variants, which returns the live color/size matrix with per-value selectability and sellable_online flags.
Call /balenciaga/store-countries for the live country-code list Balenciaga's own locator form publishes, then pass one to /balenciaga/stores for every boutique in that country — city, address, coordinates, phone, hours, and capability flags (appointments, reserve_in_store, pickup). An accepted country with no stores returns an empty list rather than an error.
On 2026-10-30 /balenciaga/categories defaulted to country ZW and language en and returned 181 categories, women's handbags reported total_results 168 over 11 pages of 16, and a product variants call returned availability and care text. Pass country explicitly.
Agent skills
Install a Crawlora agent skill and your agent can pull Balenciaga data as JSON through the documented API, without writing a scraper. These skills cover Balenciaga:
Research luxury-fashion and watch resale listings, sold evidence, condition, and seller signals across specialist marketplaces. Use for sourcing or…
npx skills add github.com/Crawlora-org/crawlora-skills --skill luxury-resale-researchFAQ
Read them from a prior response's own facets field rather than guessing — /balenciaga/search and /balenciaga/category expose live facet groups (color, category, material, selling line, stone, size, and more) with their currently valid values, which filters accepts as comma-separated field:value pairs.
A /balenciaga/product result's color variants each include their own url for the site's live Product-Variation request. Pass that url (or the original product page url) to /balenciaga/product/variants for the full color/size attribute matrix, including which combinations are selectable and sellable online.
Yes — filters on /balenciaga/search and /balenciaga/category is a comma-separated list of field:value pairs; different facet fields AND together, and repeating the same field ORs its values, for example akeneo_macroColor:BLACK,akeneo_macroColor:WHITE.
Call /balenciaga/store-countries first for the live list of accepted country codes, then pass one to /balenciaga/stores' required country parameter for every boutique the public locator publishes there.
No — only your Crawlora API key. Balenciaga's category, search, product, variant, and store data are collected from its public, credential-free storefront and locator pages.