Luxury retail pricing and colourway monitoring
Mit Prada-Endpunkten verwandelst du luxury retail pricing and colourway monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Prada's own public search index into structured luxury retail data — a full category taxonomy with breadcrumb paths and live gender counts, typo-tolerant keyword search and per-category browsing with four sort orders, per-colour product detail with sibling colourways, and search-box autocomplete with popularity ranking. Normalized JSON, credential-free, US storefront pricing.
Browse Prada's category taxonomy and gender filters, search or browse the catalogue, get full product detail, and get search suggestions as JSON.
Endpunkt-Familien
6
Dokumentierte Parameter
25
Beispiele
6
Live-Katalog-Snapshot
Aktive Endpunkte
6
Methoden
GET
Pflichtparameter
10
Schema-Referenzen
6
{
"platform": "Prada",
"endpoint": "prada-search",
"method": "GET",
"path": "/prada/search",
"auth": "apiKey"
}Use Cases
Browse Prada's category taxonomy and gender filters, search or browse the catalogue, get full product detail, and get search suggestions as JSON.
Mit Prada-Endpunkten verwandelst du luxury retail pricing and colourway monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Prada-Endpunkten verwandelst du category and gender-assortment research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Prada-Endpunkten verwandelst du search-demand and suggestion-popularity tracking in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Prada-Endpunktkatalog — 6 Endpunkte, 25 dokumentierte Request-Parameter und 6 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
6 documented Prada endpoints, grouped into 6 request families — Categories, Category and Product, plus 3 more.
25 request parameters are documented across those Prada endpoints, 10 of them required — the full input contract is public before you write any integration code.
6 of the 6 Prada endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
Prada 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.
6 hosted MCP tools back the Prada endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
Diese Karten werden aus dem aktiven Endpunktkatalog generiert, damit die Landingpage dieselbe API-Oberfläche widerspiegelt, die auch Docs und Playground nutzen.
/prada/categories
/prada/category
/prada/product
/prada/search
/prada/stores
/prada/suggest
Endpunktkatalog
/prada/searchSearches Prada's (prada.com) product catalog by keyword, through its own public search index. q is required; gender and sort are the same optional values prada-category accepts. Keyword search is typo-tolerant relevance ranking, not a guaranteed exact match. A query with genuinely zero matches returns a well-formed empty result rather than an error.
Hinweise zur Response
- Keyword search is typo-tolerant relevance ranking, not a guaranteed exact match. - A query with genuinely zero matches (for example a nonsense string) returns a well-formed empty result (`count: 0`, `products: []`) rather than an error. - Each product's `pv` is the value `prada-product`'s own `pv` parameter expects for full product-detail data. - `country` (top-level) and each product's `currency` are always `US`/`USD` -- this endpoint only ever queries Prada's US storefront. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "galleria bag", "sort": "suggested", "country": "US", "page": 1, "limit": 24, "count": 1, "total_results": 90, "total_pages": 4, "products": [ { "pv": "1BA274_2CYS_F0002_V_YO0", "model": "1BA274", "name": "Prada Galleria large leather bag", "product_type": "Galleria", "gender": ["Woman"], "color": "Black", "color_hex": "#000000", "material": "Leather", "price": 6100, "currency": "USD", "in_stock": true, "image_url": "https://www.prada.com/content/dam/pradabkg_products/1/1BA/1BA274/2CYSF0002/1BA274_2CYS_F0002_V_YO0_SLF.jpg", "url": "https://www.prada.com/us/en/p/prada-galleria-large-leather-bag/1BA274_2CYS_F0002_V_YO0" } ] } } ```
MCP-Tool prada_search
/prada/suggestReturns Prada's own search-box typeahead suggestions for a partial query -- a ranked list of suggested search phrases with the live result count each one would return. Pass a suggestion straight through to prada-search's own q parameter for product results. A query with no genuine matches returns a well-formed empty result rather than an error.
Hinweise zur Response
- Pass a suggestion straight through to `prada-search`'s own `q` parameter for product results. - `suggestions[].result_count` is the live number of products `prada-search` would return for that exact suggested query text. - `suggestions[].popularity` reflects Prada's own relative popularity ranking for that phrase (higher is more popular); it is not a product count. - A query with no genuine matches returns a well-formed empty result (`count: 0`, `suggestions: []`) rather than an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "bag", "count": 2, "suggestions": [ {"query": "bags", "result_count": 3367, "popularity": 309}, {"query": "bag charm", "result_count": 138, "popularity": 277} ] } } ```
MCP-Tool prada_suggest
/prada/categoriesReturns Prada's (prada.com) full category taxonomy -- every browsable category with its own breadcrumb path and canonical URL -- plus the two gender values products.prada.com currently carries. categories[].id is exactly the value prada-category accepts as its own category_id parameter; genders[].value is exactly what prada-search and prada-category accept as their own gender parameter.
Hinweise zur Response
- `categories[].id` is exactly the value `prada-category` accepts as its own `category_id` parameter. - `categories[].path`/`path_ids` are the ancestor breadcrumb leading to the category (not including the category itself), outermost first -- for example a "Pop Charms" category nested under Fine Jewelry > Eternal Gold returns `path: ["Fine Jewelry", "Eternal Gold"]`. - `genders[].value` is one of `Woman`, `Man` (the complete set) -- exactly what `prada-search` and `prada-category` accept as their own `gender` parameter, each with its own live product count. - `genders` is sorted by count descending, then value ascending. Example response: ```json { "code": 200, "msg": "OK", "data": { "fetched_at": "2026-09-09T12:00:00Z", "count": 214, "categories": [ { "id": "10067US", "name": "Top handles", "path": ["Womens", "Bags"], "path_ids": ["10047US", "10062US"], "url": "https://www.prada.com/us/en/womens/bags/top-handles/c/10067US" }, { "id": "11108US", "name": "Pop Charms", "path": ["Fine Jewelry", "Eternal Gold"], "path_ids": ["10614US", "10763US"], "url": "https://www.prada.com/us/en/fine-jewelry/eternal-gold/pop-charms/c/11108US" } ], "genders": [ {"value": "Woman", "count": 3867}, {"value": "Man", "count": 1830} ] } } ```
MCP-Tool prada_categories
/prada/categoryBrowses one Prada category by ID, returning every product/color variant in it. category_id is required and must be one of prada-categories' own categories[].id values. gender optionally narrows to one of prada-categories' own genders[].value values. sort selects Prada's own relevance ranking or one of its price/newest orderings. A category with no products returns a well-formed empty result rather than an error.
Hinweise zur Response
- A `category_id` with no products (a genuinely empty category) returns a well-formed empty result (`count: 0`, `products: []`) rather than an error. - An unrecognized `category_id` also returns a well-formed empty result -- validate it against `prada-categories`' own `categories[].id` values first. - Each product's `pv` is the value `prada-product`'s own `pv` parameter expects for full product-detail data. - `country` (top-level) and each product's `currency` are always `US`/`USD` -- this endpoint only ever queries Prada's US storefront. - `price_asc`/`price_desc`/`newest` are genuinely different orderings (Prada's own sort-order indices), not a client-side re-sort of the default relevance order. Example response: ```json { "code": 200, "msg": "OK", "data": { "category_id": "10062US", "sort": "suggested", "country": "US", "page": 1, "limit": 24, "count": 1, "total_results": 822, "total_pages": 35, "products": [ { "pv": "1BA274_2CYS_F0002_V_YO0", "model": "1BA274", "name": "Prada Galleria large leather bag", "product_type": "Galleria", "gender": ["Woman"], "color": "Black", "color_hex": "#000000", "material": "Leather", "price": 6100, "currency": "USD", "in_stock": true, "image_url": "https://www.prada.com/content/dam/pradabkg_products/1/1BA/1BA274/2CYSF0002/1BA274_2CYS_F0002_V_YO0_SLF.jpg", "url": "https://www.prada.com/us/en/p/prada-galleria-large-leather-bag/1BA274_2CYS_F0002_V_YO0" } ] } } ```
MCP-Tool prada_category
/prada/productReturns normalized product-detail data for one Prada product/color variant: name, price, stock, available sizes, breadcrumb, alternate colors, and images. pv is the product/color identifier, returned by prada-search's, prada-category's, and this endpoint's own products[].pv/other_colors[] fields (also the trailing path segment of a Prada product URL). description and the full image gallery are populated on a best-effort basis from the product's own page and may be briefly absent even for a valid pv; every other field is always populated. An unknown pv returns a not-found error.
Hinweise zur Response
- Unlike some other families' product-detail endpoints, a Prada product/color variant is scoped to one color at a time, matching Prada's own product page -- `other_colors[]` lists every sibling color, each with its own `pv`-bearing `url` you can pass back to this endpoint. - `description` and every image beyond the first two are populated on a best-effort basis from the product's own page, and may occasionally be briefly absent even for a valid `pv`; every other field (name, price, stock, sizes, breadcrumb, other colors) is always populated from Prada's own product index. - `discounted_price` is only set when the product currently carries a discount; otherwise it is omitted. - `in_stock` reflects Prada's own live availability signal for this color variant. - An unknown `pv` returns `404`. - A malformed `pv` (not matching Prada's own product/color identifier shape) returns `400` before any upstream request is made. - `country` and `currency` are always `US`/`USD` -- this endpoint only ever scrapes Prada's US storefront. Example response: ```json { "code": 200, "msg": "OK", "data": { "pv": "1BA274_2CYS_F0002_V_YO0", "model": "1BA274", "name": "Prada Galleria large leather bag", "description": "Leather handles---Detachable, adjustable leather shoulder strap---Removable leather key ring---External zipper pockets---Metal hardware", "product_type": "Galleria", "gender": ["Woman"], "color": "Black", "color_hex": "#000000", "material": "Leather", "country": "US", "price": 6100, "currency": "USD", "in_stock": true, "stock_quantity": 1, "sizes": [ {"label": "TU", "code": "1501"} ], "breadcrumbs": ["Womens", "Bags", "Prada Galleria"], "other_colors": [ {"name": "Black", "hex": "#000000", "code": "F0002", "url": "https://www.prada.com/us/en/p/prada-galleria-large-leather-bag/1BA274_2CYS_F0002_V_YO0"}, {"name": "Natural", "hex": "#F0E5D6", "code": "F0018", "url": "https://www.prada.com/us/en/p/prada-galleria-large-leather-bag/1BA274_2CYS_F0018_V_YO0"} ], "images": [ "https://www.prada.com/content/dam/pradabkg_products/1/1BA/1BA274/2CYSF0002/1BA274_2CYS_F0002_V_YO0_SLF.jpg", "https://www.prada.com/content/dam/pradabkg_products/1/1BA/1BA274/2CYSF0002/1BA274_2CYS_F0002_V_YO0_MDL.jpg" ], "url": "https://www.prada.com/us/en/p/prada-galleria-large-leather-bag/1BA274_2CYS_F0002_V_YO0" } } ```
MCP-Tool prada_product
/prada/storesLocates Prada's (prada.com) physical retail stores worldwide, through its own public store-locator search. All parameters are optional: with none set, this returns Prada's full worldwide store list (up to limit). query is a free-text location search (city, country, or store name); lat/lng (both required together) narrow it to a geo-radius search, optionally sized with radius_km (defaults to 50, maximum 20000). A search with genuinely zero matches returns a well-formed empty result rather than an error.
Hinweise zur Response
- With no parameters set at all, this returns Prada's full worldwide store list (up to `limit`) -- the same fallback the site's own store locator uses with an empty search box. - `distance_km` is only populated when `lat`/`lng` are given; it is the great-circle distance from the search center to the store. - `hours` reports all seven weekdays (`monday`..`sunday`) even for days the store is closed (`closed: true`, `start`/`end` omitted). Only the first open interval per day is reported. - `permanently_closed` reflects Prada's own listing status for the location, separate from `hours[].closed` (which is about that day's schedule, not whether the store is still open for business at all). - `categories` and `services` are the product departments and in-store services (e.g. private appointments, made-to-measure) Prada's own listing carries for that location; either may be empty. - A search with genuinely zero matches returns a well-formed empty result (`count: 0`, `stores: []`) rather than an error. - `lat`/`lng` provided without the other, or `radius_km` provided without `lat`/`lng`, return `400` before any upstream request is made. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "New York", "limit": 20, "offset": 0, "count": 5, "total_results": 5, "fetched_at": "2026-09-10T01:17:14Z", "stores": [ { "id": "S306", "name": "Prada New York Broadway", "line1": "575, Broadway", "city": "New York", "region": "NY", "postal_code": "10012", "country": "US", "phone": "+12123274200", "latitude": 40.7245596, "longitude": -73.9978072, "timezone": "America/New_York", "permanently_closed": false, "categories": ["Women's ready to wear", "Men's ready to wear", "Leather goods and accessories"], "services": ["Private appointment", "Made to Measure", "Made to order"], "hours": [ {"day": "monday", "start": "10:00", "end": "18:00"}, {"day": "tuesday", "start": "10:00", "end": "18:00"}, {"day": "wednesday", "start": "10:00", "end": "18:00"}, {"day": "thursday", "start": "10:00", "end": "18:00"}, {"day": "friday", "start": "10:00", "end": "18:00"}, {"day": "saturday", "start": "10:00", "end": "18:00"}, {"day": "sunday", "start": "12:00", "end": "17:00"} ] } ] } } ```
MCP-Tool prada_stores
Verwandte APIs
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.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
So scrapst du Prada
Crawlora's five Prada endpoints return category, search, product, and suggestion data as normalized JSON with one API key — Prada scopes a product/color variant one colour at a time, matching its own product page, so sibling colourways come back as separate ids rather than nested under one product.
Call /prada/categories for every browsable category with its id, breadcrumb path, and canonical URL, plus the two live genders (Woman, Man) with their own product counts. A category's id is exactly what /prada/category's category_id parameter accepts.
Pass a category_id to /prada/category, or a keyword to /prada/search's q — both accept gender (Woman or Man), sort (suggested, price_asc, price_desc, or newest, default suggested), page (1-500), and limit (default 24, max 100). A genuinely empty category or query returns a well-formed empty result rather than an error.
Pass a pv from a search or category result — also the trailing path segment of a Prada product URL — to /prada/product for description, price, stock, sizes, and breadcrumb. other_colors lists every sibling colourway, each with its own pv-bearing url to fetch that colour's own detail.
Send q to /prada/suggest for ranked phrases, each with a live result_count and a popularity score reflecting Prada's own relative ranking (higher is more popular, not a product count). Pass a suggestion straight into /prada/search's q for results.
FAQ
Pass gender to /prada/category or /prada/search — the only two accepted values are Woman and Man, as returned by /prada/categories' own genders field alongside each value's live product count.
Prada's own product page is scoped to a single colour, and /prada/product mirrors that — pv identifies one specific colour variant. other_colors lists every sibling colourway with its own pv-bearing url; fetch each one separately for that colour's own price, stock, and images.
suggested (Prada's own relevance/popularity ranking, the default), price_asc, price_desc, and newest — on both /prada/category and /prada/search. These are genuinely different upstream orderings, not a client-side re-sort of the default.
No — both a category_id with zero real products and one that does not exist return the same well-formed empty result (count: 0, products: []) rather than an error, so validate a category_id against /prada/categories first if an empty result is unexpected.
No — every price, currency, and country field across /prada/category, /prada/search, and /prada/product is fixed to US/USD; this endpoint family only queries Prada's US storefront.