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

Legacy product-ID lookup contract Identify existing requests to /products/detail using the required numeric id obtained from a product listing.
Explicit legacy store mapping Document that store comes from the country directory and is not the product-listing sideId, avoiding an unreviewed identifier substitution.
Historical locale input inventory Account for currency, lang and sizeSchema alongside store, including the unresolved numeric currency type versus USD example conflict.
Unverified-response migration boundary Keep the absence of live and example response evidence explicit so a migration does not treat any legacy output field as established.

Live API Demo

GET /api/project/asos/products-detail-deprecated

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/asos/products-detail-deprecated?key=<API_KEY>&id=<id>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →