What the Asos API does and who it is for
The Asos API mirrors the public-facing data of the Asos website and delivers it programmatically on demand. According to the provider, data is fetched live at request time with no local caching, meaning responses reflect whatever Asos currently shows on its storefront — prices, stock levels, product descriptions, and category hierarchies. This real-time characteristic makes it useful for any application that needs current inventory data rather than a periodic snapshot.
Typical consumers include price-comparison tools, fashion discovery apps, affiliate-driven storefronts, and personal shopping assistants. Researchers building datasets around fashion trends or pricing patterns also find it practical because the API surfaces structured data that would otherwise require fragile web scraping.
One thing to be clear about upfront: this is a third-party API that reproduces Asos's publicly visible data. It is not an official Asos partner integration, which has implications for long-term reliability and any commercial use cases — worth weighing before committing significant engineering effort.
Endpoint walkthrough
The API exposes 11 endpoints in total. Four of those are marked deprecated, meaning you should avoid building on them even if they still respond. The seven active endpoints cover the core use cases:
Search and discovery
- GET /v2/auto-complete — Returns autocomplete suggestions based on a partial product name. Useful for building search-as-you-type interfaces.
- GET /products/v2/list — The primary product search endpoint. Accepts filters and options so you can query by category, gender, price range, and similar facets. This is the v2 replacement for the deprecated
/products/list.
Product detail and pricing
- GET /products/v4/detail — Fetches full product information by product ID, including description, images, colour/size options, and other metadata. This is the current version; both v3 and the original
/products/detailare deprecated. - GET /products/v4/get-stock-price — Returns stock availability and current price for a given product ID. Having a dedicated stock-and-price endpoint separated from the detail endpoint is a sensible design: price and availability change frequently, so you can poll this lightweight endpoint without pulling the full product payload every time.
Taxonomy and geography
- GET /categories/list — Lists the full category tree from Asos. You would typically call this infrequently to build a local navigation structure and then use category IDs as filters when calling the product list endpoint.
- GET /countries/list — Returns the countries where Asos sells products. Helpful for localizing requests or filtering product availability by region.
Deprecated endpoints to avoid
The deprecated endpoints — /products/list, /products/v3/detail, /products/detail, /products/v2/list-similarities, and /products/v3/list-similarities — include two similarity/recommendation endpoints (v2 and v3) that have no active replacement listed. If related-product suggestions are central to your use case, confirm whether the active endpoints offer this functionality before integrating.
Performance characteristics
The reported average latency is 2,259 ms, which is on the higher end for a REST API. This is unsurprising given that responses are fetched live from the Asos site at request time rather than served from a cache. For user-facing features like a real-time search bar, you will want to account for this latency in your UX — a debounce on the autocomplete input and loading states are essentially mandatory. For background data pipelines or batch enrichment tasks, the latency is less consequential.
The average success rate is reported at 100%, which is a strong signal for reliability, though the real-time fetch model means availability is partially dependent on the upstream Asos site.
Pricing breakdown
The API uses a freemium model with four tiers:
| Plan | Monthly cost | Requests / month | Rate limit |
|---|---|---|---|
| BASIC | $0 | 500 | 5 req/s |
| PRO | $10 | 10,000 | 10 req/s |
| ULTRA | $30 | 50,000 | 10 req/s |
| MEGA | $300 | 500,000 | 15 req/s |
The free BASIC tier gives you 500 requests per month at 5 requests per second. That is sufficient for prototyping and testing your integration logic, but it will be exhausted quickly in any kind of real-world usage. If a single product detail page load triggers calls to /products/v4/detail and /products/v4/get-stock-price, you have effectively spent two requests — leaving you around 250 product views per month on the free tier.
The PRO tier at $10/month unlocks 10,000 requests, which is more workable for a small personal project or a low-traffic tool. A modestly active price-tracker that checks 100 products twice daily would consume roughly 6,000 requests per month, fitting comfortably within PRO.
ULTRA at $30/month provides 50,000 requests and the same 10 req/s rate ceiling as PRO, making it the better value for mid-scale applications. The jump to MEGA ($300/month, 500,000 requests) is a significant cost step — at that volume, you should evaluate carefully whether the economics hold relative to the use case, and whether you need the bump to 15 req/s.
Practical use cases
- Price tracking and alerts: Poll
/products/v4/get-stock-priceon a schedule for a watchlist of product IDs. At 10,000 requests per month (PRO), you can check roughly 330 products daily. - Fashion discovery apps: Combine
/v2/auto-completewith/products/v2/listto build a search interface over Asos inventory, then use/products/v4/detailto populate product pages. - Affiliate storefronts: Sync category structure via
/categories/list, hydrate product listings with/products/v2/list, and show live pricing via/products/v4/get-stock-price. - Research and analytics: Periodically snapshot product lists across categories to observe pricing trends, range changes, or discounting patterns.
Limitations and things to check before integrating
Request quotas are tight on lower tiers. 500 free requests evaporate fast. Map out your expected request volume before choosing a plan — identify every endpoint call triggered by a single user action and multiply by expected usage.
Latency at ~2.2 seconds is significant. Design your application to handle slow responses gracefully, particularly in interactive flows. Consider whether some data (categories, country lists) can be cached client-side to reduce calls.
Deprecated endpoints. The similarity/related-products endpoints are deprecated with no obvious active replacement in the current endpoint list. If recommendations are important to you, clarify this with the API provider before committing.
Third-party data source. Because this API reproduces public Asos data rather than being an official integration, its future availability depends on the provider maintaining compatibility with Asos's website. Factor this into any long-term product planning.
Getting started
Subscribing through the marketplace gives you immediate access to the BASIC tier at no cost. A practical onboarding sequence: call /categories/list first to understand the taxonomy and collect category IDs, then exercise /products/v2/list with a few category filters to verify you can retrieve product listings, and finally test /products/v4/detail and /products/v4/get-stock-price with specific product IDs from the list results. This covers the core read-path before you invest in building out a full integration.
