Get ASOS product details, images and size variants
View all ASOS Product Search, Prices & Size Availability endpoints →Retrieve a detailed ASOS product record using the required numeric id from a product listing. Optional currency, lang, sizeSchema and store values come from country discovery; use the store value, not the site identifier used by listings. A successful HTTP 200 observation used id=210916181, store=US, currency=USD, lang=en-US and sizeSchema=US. The response was an object with the matching product id and name, description, productCode, gender, brand, productType, info, media, localisedData, size flags and variants. That product was a brown leather monk shoe with brand.id=53, brand.name=ASOS DESIGN, gender=Men and productType.name=Shoes. info contained aboutMe, sizeAndFit and careInfo. media.images contained four records with url, type, colourWayId, colour and isPrimary; other media collections may be empty. The eight observed variants included id, sizeId, brandSize, displaySizeText, sizeOrder, sku, isAvailable, colourWayId and colour. For example, variant 210916195 had sizeId 388476 and displaySizeText US 7; these identifiers are distinct from product id 210916181. localisedData contained locale, title and pdpUrl records. Optional fields such as rating, shippingRestriction and fitType were null in this sample, so handle missing or empty values and variable array lengths. The observed response had no root price or isInStock field. A separate truncated source example names price, isInStock, alternateNames and brand.brandId, but those fields were not confirmed in the observed v4 record. Use the separate stock and price lookup for availability and price observations; detail variants do not provide exact stock counts, a guaranteed refresh interval or built-in price history.
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-v4-detail API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/asos/products-v4-detail?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Build a footwear inspection screen for product 210916181 using its observed ASOS DESIGN brand, Shoes classification, care information, four images and eight size variants.
- Resolve a watchlist size such as US 7 to its returned variant and size identifiers before interpreting a separate stock response, rather than treating the product ID or array index as a size.
- Prepare internal product-matching candidates from brand, gender, product type and descriptions while keeping ASOS product IDs distinct from universal retail identifiers.
- Maintain an application-managed descriptive metadata cache separately from recurring stock and price checks, choosing refresh policies without assuming a guaranteed detail lifetime.
Frequently asked questions
Which ASOS product and regional inputs were successfully observed?
The supplied successful observation returned HTTP 200 for product id 210916181 with store=US, currency=USD, lang=en-US and sizeSchema=US. It described an ASOS DESIGN brown leather monk shoe for Men. Other products and regional combinations are not established by that single observation.
Where do I get id and the optional regional values?
Use the numeric product id from a product listing. Obtain currency, lang, sizeSchema and store values from country discovery. The store value, such as US, is not the site identifier used by product listings. Only id is required.
Does the v4 detail response include current prices and exact stock counts?
The observed v4 detail object had no root price or isInStock field. Its variants included isAvailable, but that boolean does not state an inventory quantity. Use the separate stock and price lookup for those observations; neither this detail response nor the source example establishes exact stock counts or built-in price history.
How do I identify a specific size rather than the whole product?
Inspect each returned variant's id, sizeId, brandSize and displaySizeText. In the sample, product 210916181 contained variant 210916195 with sizeId 388476 and displaySizeText US 7. These are different identifiers, and an array position is not a stable size identifier.
Are eight variants and four images guaranteed for every product?
No. Those counts were observed for one footwear product. Read the returned arrays for each record, allow empty media collections and handle nullable fields such as rating, shippingRestriction and fitType.
Should I parse brandId and alternateNames from the older example?
Not as confirmed v4 fields. The observed record used brand.id and brand.name, plus localisedData records containing locale, title and pdpUrl. brand.brandId and alternateNames appeared only in a separate truncated source example, so validate actual output rather than assuming those older names.
Can I cache product descriptions separately from stock checks?
Yes, an application can store returned descriptions, brand, images and size metadata separately from recurring stock and price observations. Cache duration and refresh policy are application decisions; no built-in cache, guaranteed metadata lifetime or update interval is established by the supplied evidence.