List Burberry categories API

Endpoint facts

Method

GET

API path

/burberry/categories

Auth

apiKey

Credits

1 credit/request

Platform

Burberry

Response schema

#/definitions/burberry.categoriesResponseDoc

Overview

Lists every department, section, and leaf category from Burberry's own site navigation, flattened with a breadcrumb-style path. Each entry's url is exactly what burberry-category's own category parameter accepts. Filter to one top-level department with department (e.g. Women, Men, Children, Gifts, Trench, Scarves, Bags, Beauty & Fragrances, Sale); omit for every department. See the response's own departments field for the live list. 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

- `departments` lists every top-level department this site exposes, e.g. `Women`, `Men`, `Children`, `Gifts`, `Trench`, `Scarves`, `Bags`, `Beauty & Fragrances`, `Sale`. - `categories` includes every level of the tree, not just leaf categories -- a top-level department itself (e.g. `Women`) also appears as its own entry with `depth` 0. - `id` is the upstream's own category id (e.g. `cat10009033`) and is only present on leaf-level category nodes; higher-level department/section nodes are pure navigation groupings with no separate catalog id. - `path` is a `" > "`-joined breadcrumb of the node's ancestors, e.g. `Women > Latest > New`. Example response: ```json {"code":200,"msg":"OK","data":{"total":1,"departments":["Women","Men","Children","Gifts","Trench","Scarves","Bags","Beauty & Fragrances","Sale"],"categories":[{"id":"cat10009033","name":"New","department":"Women","path":"Women > Latest > New","url":"/l/womens-clothing/new-arrivals/","depth":2}],"source_url":"https://us.burberry.com/","fetched_at":"2026-09-09T00:00:00Z"}} ```

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