Review the deprecated ASOS product-similarity lookup contract
View all ASOS Product Search, Prices & Size Availability endpoints →Deprecated product-similarity lookup retained to identify legacy recommendation dependencies. It requires a numeric id taken from a product returned by /products/v2/list and accepts an optional string store code from /countries/list. The documented example id is 9851612 and store example is US; those examples do not establish present product availability. No successful probe is supplied for this operation. An unverified, truncated source response example shows a root id and products array whose entries contain order and product. The example product includes id, name, brandName, colour, images, isAvailable, isInStock, productCode, price and variants. Its price object includes currency, current, previous, rrp, isMarkedDown and isOutletPrice; current contains text and value. Example variants include id, brandSize, sizeId, sizeOrder, isAvailable, isInStock and isLowInStock. These are example field names, not a verified current response contract, inventory quantities or a documented similarity score. Do not assume this path still returns recommendations or that another supplied operation is an equivalent replacement. If replacing the dependency with application-defined recommendations, retrieve candidates through the current listing and inspect details separately, clearly labeling the selection logic as your own.
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-v2-list-similarities-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/asos/products-v2-list-similarities-deprecated?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Locate old related-product widgets that call /products/v2/list-similarities and mark the dependency as deprecated before planning a redesign.
- Record seed product IDs and optional store codes from existing recommendation workflows to expose product-specific and regional assumptions.
- Review archived similarity payload parsers against the unverified order/product example structure without treating that example as proof of a functioning endpoint.
- Prototype application-defined related-item selection from fresh listing candidates and product details, comparing it with archived suggestions while explicitly avoiding claims of equivalent similarity scores.
Frequently asked questions
What does the required id identify?
It is a numeric product ID from a product returned by /products/v2/list, not a category ID or a variant ID. The supplied documentation uses 9851612 as an example but does not verify that product or the deprecated lookup is currently available.
Is store required for the deprecated similarity lookup?
No. store is an optional string code obtained from /countries/list, with US as the documented example. No supplied probe establishes the behavior when it is omitted, so do not assume a regional default.
What response structure is documented, and has it been tested?
A truncated, unverified source example shows root id and products fields, with each products entry containing order and product. Nested example products include identity, image, price, availability and variant fields. No successful probe is supplied, so these fields are not a verified current response contract.
Does order represent a documented similarity score?
No similarity-score definition is supplied. The example contains an order field, but it does not establish a numeric similarity metric, stable ranking or equivalent recommendations across stores.
Is there a confirmed current replacement for this operation?
The supplied evidence does not establish an equivalent current similarity operation. You can evaluate current product-list and detail data as inputs to your own recommendation rules, but that is application-defined selection, not a drop-in replacement.
Can the example availability flags be used as exact stock quantities?
No. Fields such as isAvailable, isInStock and variant isLowInStock are flags in an unverified example, not inventory counts or a guarantee of current availability. Use separately documented stock observations for stock-related workflows.