Every Eureka Search response includes a status field. Read it on every call, because the HTTP code alone does not tell you whether the search worked.
Check the result in the InOne panel
Open your Eureka settings in the InOne panel.
Check the search configuration that applies to the query you sent, such as merchandising rules, synonyms, and strategies.
Run the same query in the storefront search and compare the results with the API response.
If the results differ, check that your request uses the same locale and currency as the storefront. Also compare the strategy (appliedSearchStrategy in the response), the user ID, and the filters and sorting.
Status values and what to do
status | Meaning | What to do |
|---|---|---|
Success | The search returned results for the query. | No action needed. |
SuccessFallback | The search returned an empty list, so the API returned items from the Recommendation API instead. These items are recommendations, not search results. | Label these results as recommendations in your interface. |
Invalid | The request failed validation, with HTTP 400. This status covers many validations, for example a query with fewer than 2 or more than 280 characters after trimming. | Read every entry in the validations array and fix the request. |
BusinessException | A business rule rejected the request, with HTTP 400. Most of these errors need a configuration change on the Insider One side, for example PartnerConfigNotFound. | Contact the Insider One team with the error.code and a sample request. |
Error | An unexpected error occurred. | Retry with exponential backoff. Show your own default results instead of an empty page. If the error continues, contact the Insider One team with the request details. |
RateLimitExceeded | You exceeded the limit of 350 requests per second for each account-locale pair, with HTTP 429. | Wait for the interval named in error.message, then retry. |
With SuccessFallback, the request worked, but the items are recommendations, not search results.
Reproduce a failure with an HTTP request
Copy the request URL and the X-AUTH-TOKEN header from your integration log.
Send the same request from your HTTP client, such as curl, with the same query, locale, currency, and X-AUTH-TOKEN header.
Compare the status value with your integration log.
Shorten or change the query until the status matches the failure.
Remove the X-AUTH-TOKEN header before you share the request or response.
To trigger a known error on purpose, send a query with one character or more than 280 characters. The API returns Invalid with HTTP 400 and a QueryInvalidLength validation.
For more information, see the Error reference section of Eureka Search API.