Locate Prada retail stores API

Endpoint facts

Method

GET

API path

/prada/stores

Auth

apiKey

Credits

1 credit/request

Platform

Prada

Response schema

#/definitions/prada.storesResponseDoc

Overview

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

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

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