Get ASOS product search suggestions
View all ASOS Product Search, Prices & Size Availability endpoints →Retrieve ASOS product-search autocomplete suggestions for the required q query string. Supply a product name, keyword or brand phrase; bikini top is a documented example, while the observed successful request used nike. The optional country, currency, lang, sizeSchema and store inputs use values from countries/list. They describe the requested market and locale context rather than filters for a specific product variant. The verified combination was country=US, currency=USD, lang=en-US, sizeSchema=US and store=US. The observed HTTP 200 body was an object with a suggestionGroups array containing one group. That group had indexName=searchterms and a suggestions array with ten entries. Each observed suggestion exposed searchTerm, the proposed query text, and numberOfResults, its reported catalog-match count. Examples were nike with 1770 results, nike women with 1530 and nike shoes with 719. These counts are observations from that request, not fixed totals, consumer search volume, sales figures or demand rankings. Group and suggestion counts are not guaranteed to remain the same. The unverified source response example also contains a group-level indexTitle field and eight suggestions; indexTitle was not confirmed by the probe metadata and should be treated as illustrative, not guaranteed. This endpoint returns query suggestions rather than product records, product IDs, prices or stock confirmation. A selected searchTerm can be passed into a separate products/v2/list search with the intended locale preserved, but suggestion presence does not guarantee that a subsequent listing request returns products. Fetching suggestions and submitting a product search are separate application actions; navigation, opening help and copying examples should not trigger either request.
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/v2-auto-complete API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/asos/v2-auto-complete?key=<API_KEY>&q=<q>'
Query Result
Use Cases
- Build an ASOS typeahead that renders returned searchTerm strings from the searchterms suggestion group for a user-entered keyword, rather than inventing completions from product titles.
- Help a catalog analyst refine a broad brand query into phrases such as nike women or nike shoes, using reported numberOfResults as catalog-match context rather than consumer-demand metrics.
- Offer query-recovery choices after an empty product listing, preserving market and locale inputs and waiting for explicit user submission before making the next listing request.
- Save autocomplete snapshots for internal merchandising vocabulary research, recording the query and locale while labeling suggestion counts as catalog observations rather than trend rankings or keyword search volume.
Frequently asked questions
What should I put in q?
Enter a product name, keyword or brand phrase. The documented placeholder is bikini top, and the successful observed query was nike. The q parameter is required; the evidence does not establish a minimum length or guarantee suggestions for every input.
How do I read the autocomplete response?
Read the top-level suggestionGroups array. In the observed response, one group had indexName=searchterms and ten suggestions. Its suggestions exposed searchTerm and numberOfResults. Iterate the returned arrays rather than assuming exactly one group or ten entries.
What does numberOfResults measure?
It is the reported catalog-match count for a suggested searchTerm, not keyword search volume, sales or consumer demand. The observed counts were 1770 for nike, 1530 for nike women and 719 for nike shoes. Those values describe one request and are not fixed totals or guaranteed future listing counts.
Which market and language values should I send?
Use country, currency, lang, sizeSchema and store values from countries/list. All five parameters are optional. The verified combination was country=US, currency=USD, lang=en-US, sizeSchema=US and store=US. Keep the intended locale consistent when submitting a selected term to product search; undocumented defaults should not be assumed.
Does a suggestion include matching products, prices or stock?
No. The observed result contains suggested query text and catalog-match counts, not product records, product IDs, prices or stock confirmation. Use a selected searchTerm in a separate products/v2/list request after user submission. A suggestion does not guarantee a nonempty follow-up response.
Is indexTitle a verified response field?
The source response example includes a group-level indexTitle field, but the observed probe metadata confirmed indexName, suggestions, searchTerm and numberOfResults rather than indexTitle. Treat indexTitle as an unverified illustrative field and do not require it to render the verified suggestion text and counts.