Implement Bloomreach Discovery autosuggest to power a search-as-you-type typeahead dropdown
domain: documentation.bloomreach.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Send a GET request to https://suggest.dxpapi.com/api/v2/suggest/?account_id=YOUR_ACCOUNT&domain_key=YOUR_DOMAIN&q={userInput}&request_type=suggest as the user types.
Debounce requests on the frontend (at least 150 ms) to avoid flooding the API on every keystroke.
Parse the response: the suggestionGroups array contains groups for query suggestions and product suggestions; render each group in the dropdown with appropriate labels.
Track the suggest event pixel when the dropdown is shown and the autosuggest_select event when the user clicks a suggestion, passing the selected term; this behavioural data feeds Bloomreach's ranking models.
For staging development, substitute the staging base URL (https://staging-suggest.dxpapi.com) and verify results before pointing to production.
Known gotchas
Autosuggest results are derived from real search queries on your site — new stores with limited traffic history may see sparse or generic suggestions until enough query data accumulates.
The auth_key is generally not required for Autosuggest (it is a public-facing client-side API) but check your account configuration; some enterprise accounts enforce it.
Query parameter q must be URL-encoded; special characters in the search term that are not encoded can corrupt the request and return errors.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?