Get related Burberry products API

Endpoint facts

Method

GET

API path

/burberry/related

Auth

apiKey

Credits

3 credits/request

Platform

Burberry

Response schema

#/definitions/burberry.relatedResponseDoc

Overview

Returns the cross-sell surfaces a real Burberry product page itself loads for that product: similar_products (algorithmically similar items) and shop_the_look (other pieces in the same styled outfit, when the upstream has curated one -- most products have none, returned as a well-formed empty list, not an error). url is the site-relative product path, e.g. /check-cashmere-cardigan-p81336111, as returned by burberry-search's, burberry-category's, or burberry-product's own url field. 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

- `similar_products` lists algorithmically similar products, in the same shape `burberry-category`/`burberry-search` use for `products[]`. - `shop_the_look` lists the other pieces in the same styled outfit, when Burberry has curated one for this product. Most products have none -- an empty list is a well-formed result, not an error. - `product_id` is the numeric id parsed out of `url`. - A `url` that is not a valid Burberry product path returns an invalid-params error. An id for a product that does not exist (or has no recommendations) still returns `200` with an empty `similar_products`/`shop_the_look`, since Burberry's own recommendations API returns the same shape either way. Example response: ```json {"code":200,"msg":"OK","data":{"url":"/check-canvas-highgate-ballerinas-p81323481","product_id":"81323481","similar_products":[{"id":"81323491","name":"Check Canvas Highgate Ballerinas","url":"/check-canvas-highgate-ballerinas-p81323491","price":695,"currency":"USD","on_markdown":false,"sold_out":false,"limited_availability":false,"image_url":"https://assets.burberry.com/is/image/Burberryltd/1928AF07"}],"source_url":"https://us.burberry.com/web-api/similar-products-recommendations?productId=81323481&experiment=MAIN&language=en&country=US","fetched_at":"2026-09-10T00: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