Burberry API endpoint
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.
/burberry/categoriesdepartment optionally filters to one top-level department (case-insensitive) -- omit for every department.
Notable 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.| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| department | string | No | Top-level department to filter to, e.g. Women, Men, Children -- omit for every department | Women | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/burberry/categories" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"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"
}
}Request schema
No body schema
Response schema
#/definitions/burberry.categoriesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | burberry.CategoriesResponse | No | ||||
| data.categories | array | No | ||||
| data.categories[].department | string | No | ||||
| data.categories[].depth | integer | No | Depth is 0 for a top-level department, 1 for its direct sections, and so on. | |||
| data.categories[].id | string | No | ID is the upstream's own category id (e.g. "cat10009033") when the node carries one -- only leaf-level category nodes do; higher-level department/section nodes are pure navigation groupings with no separate catalog id, so ID is empty for those. | |||
| data.categories[].name | string | No | ||||
| data.categories[].path | string | No | Path is a " > "-joined breadcrumb of this node's ancestors, e.g. "Women > Latest > New". | |||
| data.categories[].url | string | No | ||||
| data.departments | array | No | ||||
| data.fetched_at | string | No | ||||
| data.source_url | string | No | ||||
| data.total | integer | No | ||||
| msg | string | No | OK |
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/burberry/categories" \
-H "x-api-key: $CRAWLORA_API_KEY"