Retail category monitoring
Use Lululemon endpoints to turn retail category monitoring into repeatable API requests with documented inputs and JSON responses.
Turn lululemon's storefront data into structured retail data — category navigation and product listings with pricing and sale detection, full per-SKU product detail with live availability and customer reviews, curated outfit recommendations, and the physical store directory, all as normalized JSON. Credential-free.
Browse lululemon categories and products, get full product detail with pricing and reviews, get outfit picks, and find stores — as structured JSON.
Endpoint families
5
Documented params
18
Examples
0
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
10
Schema refs
5
{
"platform": "Lululemon",
"endpoint": "lululemon-category",
"method": "GET",
"path": "/lululemon/category",
"auth": "apiKey"
}Use cases
Browse lululemon categories and products, get full product detail with pricing and reviews, get outfit picks, and find stores — as structured JSON.
Use Lululemon endpoints to turn retail category monitoring into repeatable API requests with documented inputs and JSON responses.
Use Lululemon endpoints to turn sale and price tracking into repeatable API requests with documented inputs and JSON responses.
Use Lululemon endpoints to turn product catalog and review research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/lululemon/categories
/lululemon/category
/lululemon/outfit
/lululemon/product/{product_id}
/lululemon/stores
Endpoint catalog
/lululemon/categoriesReturns lululemon's own storefront category navigation, flattened out of the site's shared header nav: every navigable category with its display name, breadcrumb path, and the exact category/cdp_hash pair lululemon-category's own parameters expect (read directly from the nav's own URL, not guessed from the display label). section, when given, filters the result to one top-level nav section.
/lululemon/categoryReturns one lululemon category's product listing page: normalized products with pricing, sale detection, sizes, colors, and style numbers, sourced from lululemon's own app-backend category data. category and cdp_hash are the two path segments of a lululemon category URL (https://shop.lululemon.com/c/{category}/{cdp_hash}), e.g. women-new-styles and n14f1wz6o10 -- both are also available from lululemon-categories's own category and cdp_hash fields. Pagination is page-based and real: requesting a page beyond the category's real last page returns a normal response with an empty products array rather than an error. An unrecognized category/cdp_hash pair returns 404.
/lululemon/product/{product_id}Returns one lululemon product's full detail: every purchasable color/size SKU with its own price, sale status, and live availability, plus an aggregate rating and real customer reviews when the product has any -- none of which lululemon-category exposes (it only carries one representative color/price per product). product_id is the id from a lululemon-category result's id field or a lululemon product URL's trailing path segment (https://shop.lululemon.com/p/{slug}/{product_id}) -- the slug itself is not needed. An unrecognized product_id returns 404.
/lululemon/outfitReturns lululemon's own curated outfit/style recommendations for one product color: every complementary item in each styled look, plus the anchor product itself. unified_id and color_code are lululemon-product's own unified_id response field and a color's code field (from lululemon-product's colors[] or lululemon-category's style_numbers-paired colors[]) -- not lululemon-product's own product_id, which is a different id space. Recommended items' own id is a separate, third-party catalog id (not lululemon-product's product_id) -- use each item's url to reach its product page. An unrecognized unified_id/color_code pair returns 404.
/lululemon/storesReturns 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.
Related 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.
How to scrape Lululemon
Crawlora's 5 Lululemon endpoints return category navigation, category listings, product detail, outfit recommendations, and the physical store directory as normalized JSON with one API key — no lululemon account required.
Call /lululemon/categories for lululemon's own storefront nav, flattened — every category's display name, breadcrumb path, and the exact category/cdp_hash pair /lululemon/category expects. Pass section (new-featured, women, men, accessories, bags, activity, or we-made-too-much) to filter to one nav section.
Pass a category and cdp_hash — from /lululemon/categories, or the two path segments of a lululemon category URL (https://shop.lululemon.com/c/{category}/{cdp_hash}) — to /lululemon/category for that page's normalized products: pricing, sale price, sizes, colors, and style numbers, with real page-based pagination.
Pass a product's id (from a category result's id field, or a product URL's trailing path segment) to /lululemon/product/{product_id} for every purchasable color/size SKU with its own price, sale status, and live availability, plus an aggregate rating and customer reviews when the product has any.
Pass a product's unified_id and a color's code (both from a /lululemon/product result) to /lululemon/outfit for lululemon's own curated styled looks — every complementary item in each look, plus the anchor product.
Call /lululemon/stores for the full US/Canada store directory with weekly hours and amenities. Filter locally by country/state (free-text 2-letter codes), or pass lat+lng for a nearest-first radius search (radius_miles, 1-500, defaults to 50) — there's no live geo-search API on lululemon's own credential-free surface, so filtering happens against the full fetched directory.
FAQ
Call /lululemon/categories for the full storefront nav, flattened — each entry's category and cdp_hash are read directly from the nav's own URL, ready to pass straight into /lululemon/category. You can still build a category/cdp_hash pair from a known storefront URL instead.
/lululemon/category's pagination is real and page-based. Requesting a page beyond the category's real last page returns a normal response with an empty products array rather than an error.
Not directly — there's no free-text search endpoint. /lululemon/categories covers nav-tree discovery, and /lululemon/category covers per-category browsing, but neither takes a keyword query.
Pass the product's id (from a /lululemon/category result's id field, or a product URL's trailing path segment) to /lululemon/product/{product_id}. Unlike /lululemon/category — which only carries one representative color/price per product — this returns every SKU's own price, sale status, and live availability, plus the aggregate rating and customer reviews.
Pass a /lululemon/product result's unified_id and a colors[].code value to /lululemon/outfit. Note unified_id and color_code are a different id space from /lululemon/product's own product_id — an unrecognized pair returns 404.
Yes — pass lat and lng (both required together) to /lululemon/stores for a nearest-first list within radius_miles (1-500, defaults to 50). country and state are optional free-text 2-letter-code filters. All filtering runs locally over lululemon's full directory, since there's no live geo-search endpoint on a credential-free host.