Look up legacy ASOS product details (deprecated)
View all ASOS Product Search, Prices & Size Availability endpoints →Deprecated ASOS product-detail lookup retained for identifying and migrating existing integrations, not recommended for new catalog enrichment. The required numeric id is obtained from a product listing. Optional currency, lang, sizeSchema and store values are documented as coming from the country directory; the examples are USD, en-US, US and US respectively. store is the country directory's store value, not the product-listing sideId. No defaults for omitted inputs are documented. The legacy currency field is declared numeric even though its documented example is USD; this conflicting input contract remains unverified and neither numeric nor text currency handling should be assumed. No live probe or response example was supplied for this deprecated operation. Its stated purpose is product-detail retrieval, but no returned fields, response shape, current availability or compatibility with newer detail records can be verified from the supplied evidence. Use products-v4-detail as the migration target for review, with explicit field and locale comparisons rather than assuming drop-in compatibility.
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-detail-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/asos/products-detail-deprecated?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Audit an existing codebase for calls to /products/detail and record each consumer's product ID and locale inputs before changing routes.
- Plan an opt-in comparison with products-v4-detail for a known product, treating legacy availability and field compatibility as questions to verify.
- Preserve historical field-mapping notes for archived product records without presenting this deprecated operation as a current enrichment source.
- Flag migration risks caused by substituting sideId for store or assuming that the conflicting currency type and USD example define a valid request.
Frequently asked questions
Should I use this deprecated detail endpoint for a new integration?
No. It is retained for legacy discovery and migration planning. Review products-v4-detail for a new detail workflow, but do not assume the two routes accept identical inputs or return compatible fields.
Where do the product ID and store inputs come from?
id is the required numeric product identifier obtained from a product listing. The optional store value comes from the country directory; the documented example is US. It is not the sideId used by a product listing.
Why does the numeric currency field show USD as its example?
The documented legacy contract is inconsistent: currency is declared numeric while its example is USD. No supplied live response resolves the conflict. The type and example are preserved for review, not evidence that either form is accepted.
Which response fields have been verified for this route?
None. No live probe or response example was supplied for this deprecated operation, so no field names, response shape, stock information or current availability are established. Verify any legacy field mapping explicitly during a controlled migration.
Are the language and size-schema examples guaranteed defaults?
No. en-US and US are documented examples for lang and sizeSchema, not established omission defaults. Choose appropriate settings from the country directory and review how the existing integration uses them before migrating.