Lululemon Store Directory API

Endpoint facts

Method

GET

API path

/lululemon/stores

Auth

apiKey

Credits

3 credits/request

Platform

Lululemon

Response schema

#/definitions/lululemon.storesResponseDoc

Overview

Returns lululemon's own complete physical store directory (480 US and 86 Canada locations as of this endpoint's own research), including regular weekly hours and in-store amenities. All filters are optional and applied locally after fetching the full directory -- there is no live geo-search API on a credential-free host for this platform (see notes/lululemon-maintenance.md). country and state are free-text equality filters against the values this directory actually carries (2-letter codes, e.g. US/CA, NY/CA), not an enforced enum. lat and lng (both required together) filter to stores within radius_miles (1 to 500, defaults to 50), sorted nearest-first. 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

3 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

- Omitting every filter returns the complete directory. - `hours[]` is regular (non-holiday) weekly hours, sorted Monday-first — the upstream's own array order is alphabetical by day name, not calendar order. - `distance_miles` is populated only when `lat`/`lng` were given. - `status` and `store_type` are passed through as free strings (e.g. `active`, `regular`) rather than an enforced enum — the site's own UI shows additional states (`Opening Soon`, `Closed`) not yet captured in this field's raw upstream value, so unrecognized values are not dropped. - `message`, when non-empty, is a store-specific notice from the upstream (e.g. a temporary closure note). ```json {"code":200,"msg":"OK","data":{"count":1,"source_url":"https://shop.lululemon.com/stores/all-lululemon-stores?locale=en_US&sl=US","fetched_at":"2026-08-14T09:00:00Z","stores":[{"id":"00500","name":"The Shops at Hudson Yards","slug":"/stores/us/new-york/hudson-yards","url":"https://shop.lululemon.com/stores/us/new-york/hudson-yards","address":"500 West 33rd Street, RU 313A, New York, NY, US, 10001","city":"New York","state":"NY","state_name":"New York","country":"US","latitude":40.7538,"longitude":-74.0022,"store_type":"regular","status":"active","hours":[{"day":"monday","open":"10:00","close":"21:00"},{"day":"friday","open":"10:00","close":"21:00"}],"amenities":{"footwear":true,"has_mirror":false,"personal_shopping":true,"like_new":true,"buy_online_pickup_store":true,"curbside_pickup":true,"complementary_hemming":true,"returns_exchanges":true}}]}} ```

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