List legacy v3 ASOS similar products (deprecated)
View all ASOS Product Search, Prices & Size Availability endpoints →Deprecated similar-product lookup for an existing ASOS product. Supply the required numeric id returned by a product listing. Optional currency, lang, sizeSchema and store preserve the regional request context; documented examples are USD, en-US, US and US. Select currency, sizing and store values from country discovery and use lang for the language code. No live response was supplied for this deprecated route, so present-day recommendation behavior and availability are unverified. A truncated source example has a root id and products array; each visible entry has order and a nested product. Product fields in that unverified excerpt include id, name, brandName, colour, images, price, variants, isAvailable and isInStock. Visible price fields include currency, current, previous and rrp; visible variant fields include brandSize, sizeId, sizeOrder and isLowInStock. Treat these as source-only structural clues, not confirmed outputs, similarity scores, exact inventory quantities or a guaranteed ranking contract. No current non-deprecated similarity replacement is established by the supplied evidence. A category-listing fallback can support separate discovery, but must not be presented as equivalent recommendations from this endpoint.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/asos/products-v3-list-similarities-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/asos/products-v3-list-similarities-deprecated?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Inventory regional recommendation widgets that still send a seed product ID with currency, language, sizing and store selections to the deprecated v3 route.
- Test an older recommendation parser against retained fixtures containing products, order and nested product records while recording the lack of current live verification.
- Plan a separately labeled category-discovery fallback for unavailable similarity results rather than silently substituting it as an equivalent recommendation feed.
- Write a retirement checklist for a legacy similar-products carousel, covering missing results, optional product fields and the absence of a verified replacement endpoint.
Frequently asked questions
Which product ID should I use to request legacy similar products?
Use the numeric id returned by a product listing. It is the only required query input and identifies the starting product for the documented similarity lookup; it is not a category or variant ID.
Has the deprecated v3 similarity response been live-verified?
No live response was supplied. The available source example is truncated and shows products entries with order and nested product fields, but it does not establish a currently working response contract.
Does order represent a measured similarity score?
That is not documented. The source excerpt contains an order field, but no supplied evidence defines a similarity score or guarantees ranking behavior. Do not convert that field into a confidence score.
How do I retain the context of older regional recommendation requests?
Record currency, lang, sizeSchema and store alongside the seed id. Documented examples are USD, en-US, US and US. Currency, sizing and store values come from country discovery; these examples do not establish defaults or verified localized results.
Is category filtering an equivalent replacement for this endpoint?
No. No verified non-deprecated similarity replacement is established here. Filtering category listings and inspecting shortlisted products can support a separate discovery flow, but must not be labeled as this endpoint's recommendations or as equivalent similarity results.