API Error Codes

These are some error codes used by the Search APIs.

Error Code

Description

400

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

Some sample error messages:

  • Invalid or empty search_type
  • Pagination limit exceeded: requested start 0, rows 216. Max start 10000, rows 200
  • price expects a number or range, instead got $1,000-$100,000
  • rows should be >=0
  • Error parsing sort=
  • invalid account_id None
  • 403

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

    414 URI Too Long

    This happens when the URI is over 16K Bytes. Check for high number of configurations in Facet Manager, or contact Support to debug.

    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.

    431 Request Header Fields Too Large

    This happens when the request header is too large. Check for high number of configurations in Facet Manager, or contact Support to debug.

    500 Internal Server Error

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

    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.

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

    {
      "status_code": 400,
      "message": "[u'invalid account_id 0']"
    }