Retrieve legacy v3 ASOS product details (deprecated)
View all ASOS Product Search, Prices & Size Availability endpoints →Deprecated product-detail lookup retained for existing v3 clients and migration planning. Supply the required numeric id obtained from a product listing. Optional currency, lang, sizeSchema and store values should come from country discovery; the documented examples are USD, en-US, US and US respectively. The store input is the country-discovery store value, not the site identifier used by product listings. No live response was supplied for this deprecated endpoint, so its current availability and response contract are unverified. A truncated source example names id, name, productCode, brand, alternateNames, info, media, price, variants and isInStock. In that unverified excerpt, alternateNames contains locale and title, brand includes brandId and name, info includes aboutMe, careInfo and sizeAndFit, media includes images and catwalk entries, and price includes currency, current, previous and rrp. The variants excerpt includes brandSize, isAvailable and isLowInStock but is incomplete. These source-only fields are migration clues, not confirmed current outputs or exact stock quantities. For new detail integrations, evaluate products-v4-detail and compare saved fixtures before switching; do not assume identical variant, media or price structures.
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-detail-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/asos/products-v3-detail-deprecated?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Map an existing v3 detail client's five query inputs to a planned v4 request without confusing the store value with a listing site identifier.
- Create fixture-based migration tests for legacy brand, media, price and variant parsing, checking the v4 contract independently.
- Annotate archived v3 catalog records with their deprecated lookup version so historical field shapes are not mistaken for current responses.
- Audit optional-field assumptions in a legacy product detail page before replacing its v3 lookup with products-v4-detail.
Frequently asked questions
Is this v3 detail endpoint verified for new integrations?
No. It is deprecated and no live response was supplied for it. Its source example is truncated and unverified. Evaluate products-v4-detail for new work and validate any migration against actual response fixtures.
Which inputs are required for the legacy product lookup?
Only id is required, and it is a numeric product identifier obtained from a product listing. currency, lang, sizeSchema and store are optional query inputs. Their documented examples are USD, en-US, US and US; these examples are not confirmed server defaults.
Should store contain the site identifier from product listings?
No. The documented store input comes from country discovery and uses a value such as US. It is explicitly different from the site identifier used by product listings.
Can I depend on the v3 example's variant and stock fields?
Not as a current response guarantee. The truncated source example names variants, brandSize, isAvailable, isLowInStock and isInStock, but no live v3 output confirms them. Availability flags also do not establish exact inventory quantities.
Can I switch to v4 without changing my response parser?
That has not been established. The cataloged inputs overlap, but the v3 response is not live-verified. Compare saved v3 fixtures with v4 output, especially variant, media and price structures, before reusing a parser.