Browse ASOS category products with regional filters and pagination

View all ASOS Product Search, Prices & Size Availability endpoints →

List products for a category using required numeric categoryId, offset and limit plus the required string store from country discovery. Optional country, currency, lang and sizeSchema define the regional context. Documented filters include comma-separated brand, size, base_colour and attribute IDs, integer priceMin/priceMax bounds, range, and freshness/priceasc/pricedesc sorting. The supplied US category probe used categoryId=4209, offset=0, limit=10 and freshness sorting; HTTP 200 returned categoryName='Shoes, Boots & Sneakers', itemCount=1523, ten products and ten facets. The first observed product was ID 210916181, ASOS DESIGN two strap monk shoes, with a current USD price of 94.99. Treat itemCount as a reported count, not the number of rows in the current page or proof of complete coverage. A separate keyword probe returned HTTP 200 with itemCount=0, products=[], facets=[], categoryName=null and searchPassMeta.isPartial=false and isSpellcheck=false; its searchTerm echoed the supplied term twice, separated by a comma. This does not establish a universal cause for empty searches. The q notes say not to combine it with categoryId, yet categoryId remains required in this published contract; the keyword-only probe does not remove that constraint. The supplied truncated example additionally documents diagnostics and facets[].facetValues[] entries with id, name, count and isSelected, plus facet metadata such as displayStyle, facetType and hasSelectedValues. Those nested example fields and optional filter combinations are not independently established by the probe summaries. Save product IDs for separate detail or stock checks; listing data does not provide exact inventory quantities, sales rankings or built-in price history.

API Features

Observed US footwear assortment page A supplied category 4209 probe returned ten products and an itemCount of 1523, with product 210916181 available as a concrete ID for follow-up checks.
Comma-separated current-list facets Brand, colour, size and attribute filters are documented as comma-separated ID strings. Derive choices from category metadata rather than inventing an enum.
Regional pagination context Keep store, country, currency, language and size schema fixed while using offset and limit to collect a bounded category sample.
Empty-search diagnostic signals The supplied nonexistent-term probe returned empty products and facets with itemCount=0. Preserve searchTerm and searchPassMeta flags when investigating an empty result.
Reported count versus returned rows Distinguish the reported itemCount from products.length and deduplicate saved product IDs; neither count nor listing position establishes sales or popularity.

Live API Demo

GET /api/project/asos/products-v2-list

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-v2-list?key=<API_KEY>&categoryId=<categoryId>&limit=<limit>&offset=<offset>&store=<store>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

How does itemCount differ from the products array length?

itemCount is the count reported for the result context, while products contains the returned page. The supplied category probe reported itemCount=1523 but returned ten products with limit=10. It does not prove that every reported item can be collected.

Which regional and pagination inputs should a category request keep consistent?

Provide required store, categoryId, offset and limit, and choose matching country, currency, lang and sizeSchema values from country discovery where available. The successful sample used store=US, country=US, currency=USD, lang=en-US, sizeSchema=US, categoryId=4209, offset=0 and limit=10.

Can I combine q with categoryId, or omit categoryId for keyword search?

The q documentation says not to combine it with categoryId, but categoryId is still required in this published operation contract. The supplied keyword-only probe omitted categoryId and returned an empty result; that evidence does not make categoryId optional here or establish a valid keyword-only request in this contract.

How are multiple filter choices and price bounds represented?

The current listing documents comma-separated IDs for brand, size, base_colour and attribute filters. priceMin and priceMax are numeric fields documented as integer price bounds. The category probe did not independently test these filter combinations, so use actual facet IDs and verify the result context.

Does an empty products array mean that keyword search is broken?

No. A supplied nonexistent-term probe returned HTTP 200 with itemCount=0, empty products and facets, categoryName=null and false isPartial/isSpellcheck flags in searchPassMeta. Its searchTerm contained the supplied query twice, but this single observation does not establish a universal explanation for empty searches.

Can this listing establish stock quantities or historical prices?

No. The supplied category observation includes product IDs, names and a current USD price, not exact inventory quantities or a built-in historical series. Use separate detail or stock operations for their documented fields, and store your own timestamped observations if you need comparisons over time.

Related operations

Guides

View Subscription Plans →