Review the deprecated ASOS category product listing contract
View all ASOS Product Search, Prices & Size Availability endpoints →Deprecated category-based product listing retained for migration reference. Supply categoryId from category discovery, store from the country record's siteId, and the required offset and limit query values. Optional country, currency, lang and sizeSchema select the regional context; brand, size, base_colour and attribute filters narrow the category, while min and max are documented as integer price bounds. The documented sort values are freshness, priceasc and pricedesc. This legacy contract does not list a q parameter, so do not assume it supports the keyword search available in the current listing contract. Parameter documentation references facetValues[].id for range, colour, brand and size filter choices. No response example or successful probe is supplied for this deprecated endpoint, so its product fields, response envelope, pagination metadata and present availability are unverified. When moving to /products/v2/list, explicitly review min/max versus priceMin/priceMax and recheck saved filters rather than treating the paths as aliases.
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-list-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/asos/products-list-deprecated?key=<API_KEY>&categoryId=<categoryId>&limit=<limit>&offset=<offset>&store=<store>'
Query Result
Use Cases
- Inventory category collectors that still use /products/list and record their categoryId, store, offset and limit settings before a migration.
- Build a price-filter migration checklist that maps legacy min/max intent to the current priceMin/priceMax inputs without assuming identical results.
- Review saved brand, size, colour and attribute selections for stale facet IDs while preserving their original regional context.
- Plan a controlled legacy-versus-current category comparison only if legacy access is available, keeping keyword-search tests separate because this contract has no q input.
Frequently asked questions
Should a new category browser use this deprecated operation?
Use /products/v2/list as the current listing contract to evaluate. This deprecated path is retained for migration reference, and no successful probe or response example is supplied for it.
Which inputs are required by the legacy listing contract?
categoryId, store, offset and limit are required. categoryId comes from category discovery, and store is the siteId value in the relevant country record. Keep the region and pagination choices explicit when comparing old requests.
Can I send a keyword through q on this operation?
The supplied legacy contract does not declare q. Do not add it or promise keyword-search equivalence; evaluate the current listing operation's documented search inputs instead.
Are the legacy price filters named priceMin and priceMax?
No. This operation declares min and max, both numeric inputs documented as integer price bounds. The current listing uses priceMin and priceMax, so review that mapping explicitly during migration.
Where do filter IDs come from, and are response fields verified?
The parameter notes reference facetValues[].id for range, colour, brand and size choices and describe repeated query keys for several filters. No response sample or successful probe is supplied here, so the response envelope, product fields and repeated-filter behavior are not verified.