Prada Category & Gender API

Endpoint facts

Method

GET

API path

/prada/categories

Auth

apiKey

Credits

2 credits/request

Platform

Prada

Response schema

#/definitions/prada.categoriesResponseDoc

Overview

Returns 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. 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

2 credits/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

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

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