Burberry API endpoint
Returns one page (20 products) of a Burberry category/browse listing. category is the site-relative category path, e.g. /l/womens-clothing/new-arrivals/ -- use burberry-categories to discover every valid value instead of guessing from site URLs. offset paginates in increments of 20 (the upstream's own fixed page size). sort selects the result order. The response includes the upstream's own available filters (facets) with live per-option result counts; feed a selection back in via facets, a comma-separated list of property:value pairs taken from this same response's facets field (e.g. benefit:bags,dotcomreportingcolour:black -- see a live response for the values valid for that category). At most one value per facet property; an unmatched or invalid combination returns a well-formed empty result, not an error.
/burberry/categoryoffset is zero-based and paginates in increments of 20 (the upstream's own fixed page size). sort accepts default, price_asc, price_desc, or newest and defaults to default. facets is optional and applies a facet filter selection: a comma-separated list of property:value pairs taken directly from this same response's own facets field, e.g. benefit:bags,dotcomreportingcolour:black. At most one value per property is supported.
Notable response behavior:
total_products reports the upstream's true total for this category (or for the applied facet selection, when facets is set), regardless of page size.url is the value to pass as url to burberry-product.facets lists the upstream's own available filters (category, colour, size, price range, and others depending on the category) with live per-option result counts -- each options[].value combined with the parent facet's own name is a valid property:value entry for this request's own facets parameter.applied_facets echoes back the facets parameter that was applied, when one was given.facets combination (e.g. a typo'd value, or two values from different categories that never co-occur) returns a well-formed empty products list with total_products 0, not an error -- the same way an unmatched search query behaves.on_markdown and original_price indicate a markdown/sale price; original_price is only set when the product carries a former price.sold_out and limited_availability are the upstream's own stock-status flags.| Field | Filled in, of 20 checked | Values in the sample |
|---|---|---|
| id | 20 | |
| name | 20 | “Mini Note Bag” and 14 other values |
| url | 20 | “/mini-note-bag-p81382941” and 19 other values |
| price | 20 | 840 to 2,795, median 1,550 |
| currency | 20 | USD in all 20 |
| on_markdown | 20 | true in 0 of 20 |
| color | 20 | “Archive beige/briar brown” and 11 other values |
| number_of_colours | 20 | 1 to 5, median 1 |
| sold_out | 20 | true in 0 of 20 |
| limited_availability | 20 | true in 0 of 20 |
| image_url | 20 | assets.burberry.com |
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| category | string | Yes | Site-relative category path -- see burberry-categories | /l/womens-clothing/new-arrivals/ | |
| offset | integer | No | Zero-based result offset, in increments of 20 Minimum: 0. Maximum: 100000. | ||
| sort | string | No | Sort order Allowed values: default, price_asc, price_desc, newest. | ||
| facets | string | No | Comma-separated property:value facet filters, taken from this same response's own facets field, e.g. benefit:bags,dotcomreportingcolour:black -- at most one value per property | benefit:bags | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/burberry/category?category=%2Fl%2Fwomens-clothing%2Fnew-arrivals%2F&sort=default" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"msg": "OK",
"data": {
"category": "/l/womens-clothing/new-arrivals/",
"offset": 0,
"sort": "default",
"total_products": 132,
"count": 1,
"products": [
{
"id": "81336111",
"name": "Check Cashmere Cardigan",
"url": "/check-cashmere-cardigan-p81336111",
"price": 1995,
"currency": "USD",
"on_markdown": false,
"color": "Ecru beige",
"number_of_colours": 2,
"sold_out": false,
"limited_availability": false,
"image_url": "https://assets.burberry.com/is/image/Burberryltd/47C2F220"
}
],
"facets": [
{
"name": "benefit",
"label": "Category",
"options": [
{
"value": "bags",
"label": "Bags",
"count": 131
}
]
}
],
"applied_facets": "benefit:bags",
"source_url": "https://us.burberry.com/l/womens-clothing/new-arrivals/benefit=bags/",
"fetched_at": "2026-09-09T00:00:00Z"
}
}Request schema
No body schema
Response schema
#/definitions/burberry.categoryResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | burberry.CategoryResponse | No | ||||
| data.applied_facets | string | No | AppliedFacets echoes back the facets parameter that was applied to this request, if any. | |||
| data.category | string | No | ||||
| data.count | integer | No | ||||
| data.facets | array | No | Facets lists the upstream's own available filters (category, colour, size, price range, and others depending on the category) with live per-option result counts. Feed a selection back in via this request's own facets parameter (property:value, taken from a Facet's Name and one of its Options' Value). Facet record, 6 fields: label, name, options. Described under Search Burberry products API. | |||
| data.fetched_at | string | No | ||||
| data.offset | integer | No | ||||
| data.products | array | No | Product record, 12 fields: color, currency, id, image_url, limited_availability, name, number_of_colours, on_markdown, original_price, price, sold_out, url. Described under Search Burberry products API. | |||
| data.sort | string | No | ||||
| data.source_url | string | No | ||||
| data.total_products | integer | No | ||||
| msg | string | No | OK |
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/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/category?category=%2Fl%2Fwomens-clothing%2Fnew-arrivals%2F&sort=default" \
-H "x-api-key: $CRAWLORA_API_KEY"