Browse a Prada category API

Endpoint facts

Method

GET

API path

/prada/category

Auth

apiKey

Credits

1 credit/request

Platform

Prada

Response schema

#/definitions/prada.categoryResponseDoc

Overview

Browses 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. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- 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" } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related