Search Burberry products API

Endpoint facts

Method

GET

API path

/burberry/search

Auth

apiKey

Credits

3 credits/request

Platform

Burberry

Response schema

#/definitions/burberry.searchResponseDoc

Overview

Searches Burberry's product catalog by keyword. Returns normalized product summaries plus the upstream's own available filters (facets) with live per-option result counts. offset paginates in increments of 20 (the upstream's own fixed page size). sort selects the result order. facets applies a facet selection back, a comma-separated list of property:value pairs taken from this same response's facets field (e.g. benefit:bags,dotcomreportingcolour:black). A query with no matches, or a facet combination with no matches, returns a well-formed empty result, not an error. Unlike burberry-category, this response has no true grand-total result count -- only the current page's own count. 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

- A query with no matches, or a `facets` combination with no matches, returns a well-formed empty `products` list, not an error. - Unlike `burberry-category`, this response has no true grand-total result count in the upstream data -- `count` is only the current page's own result count. - `facets` lists the upstream's own available filters with live per-option result counts, same as `burberry-category` -- 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. - Each product's `url` is the value to pass as `url` to `burberry-product`. Example response: ```json {"code":200,"msg":"OK","data":{"query":"trench","offset":0,"sort":"default","count":1,"products":[{"id":"80830751","name":"Short Camden Heritage Car Coat","url":"/short-camden-heritage-car-coat-p80830751","price":2295,"currency":"USD","on_markdown":false,"color":"Coal blue","number_of_colours":3,"sold_out":false,"limited_availability":false,"image_url":"https://assets.burberry.com/is/image/Burberryltd/5FF320CA"}],"facets":[{"name":"colour","label":"Colour","options":[{"value":"black","label":"Black","count":5}]}],"applied_facets":"","source_url":"https://us.burberry.com/search?query=trench","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