Error Codes - Bloomreach Experience - Open Source CMS

Error Codes

Following is a list of error codes that are used by the Bloomreach Search and Merchandising APIs:

Error Code

Description

400

This happens mostly due to invalid parameters in the API request.

A few sample error messages for this issue are given below:

{"status_code": 400, "message": "[u'Invalid or empty search_type']"} {"status_code": 400, "message": "[u'Pagination limit exceeded: requested start 0, rows 216. Max start 10000, rows 200']"} {"status_code": 400, "message": "[u'price expects a number or range, instead got $1,000-$100,000']"} {"status_code": 400, "message": "[u'rows should be >=0']"} {"status_code": 400, "message": "[u'start should be >=0']"} {"status_code": 400, "message": "[u'Error parsing sort=']"} {"status_code": 400, "message": "[u'invalid account_id None']"}

403 This happens when the auth_key in the request is either empty or incorrect.

429

Rate limit error

Usually happens when there is a high load on the merchant search, or during load testing. Retrying this when the load is less gets the response.

500

Internal Server Error
 

Servers are not working as expected. The request is probably valid but needs to be requested again later.

Note: If the frequency of this issue is high, reach out to your Bloomreach representative during integration and the Bloomreach support team post going live.

504

Gateway timeout Error
 

This happens rarely and retrying after a certain interval usually fixes this issue.

543

Timeout Error

Server did not receive a complete request from the client within a specific period of time.

Note: If the frequency of this issue is high, reach out to your Bloomreach representative during integration and the Bloomreach support team post going live.
Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?