Lululemon Category Navigation API

Endpoint facts

Method

GET

API path

/lululemon/categories

Auth

apiKey

Credits

3 credits/request

Platform

Lululemon

Response schema

#/definitions/lululemon.categoriesResponseDoc

Overview

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

- `category` and `cdp_hash` are read directly from the nav's own URL for every single entry, not guessed or derived from the display label -- unlike this repo's H&M-family precedent, where a real `category_id` is only present for a confirmed subset of entries. - `path[]` is the breadcrumb of parent nav labels above the entry (e.g. `["Women", "Women's Clothes"]`); empty for a top-level section's own direct category. - A section can itself be a direct category (`path` empty, `name` equal to the section's own display name) in addition to any nested subcategories underneath it. - `activity` currently resolves to zero categories -- its nav node carries no category link of its own at capture time -- but remains a valid `section` value since nothing rules out the site populating it later. ```json {"code":200,"msg":"OK","data":{"source_url":"https://shop.lululemon.com/?locale=en_US&sl=US","fetched_at":"2026-08-14T08:00:00Z","count":2,"categories":[{"section":"women","name":"Women's Clothes","url":"https://shop.lululemon.com/c/women-clothes/n14uwk","category":"women-clothes","cdp_hash":"n14uwk"},{"section":"women","path":["Women's Clothes"],"name":"Scuba","url":"https://shop.lululemon.com/c/women-scuba-clothes/n14uwkz9uld","category":"women-scuba-clothes","cdp_hash":"n14uwkz9uld"}]}} ```

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