Errors

The BIDEX API uses standard HTTP status codes. Every error response contains a JSON body with the error name, message, status and a requestId you can quote when contacting support.

{
  "err": {
    "name": "BidexValidationError",
    "from": "connections-backend",
    "message": "Invalid format parameter. Must be \"json\" or \"csv\".",
    "status": 400,
    "requestId": "a1b2c3d4-...",
    "logid": "..."
  }
}

Status codes

Status	Meaning	What to do
200	The request succeeded	Save or process the downloaded file
400	A parameter has an invalid format	Check BuyersID, format, language, country and currency
401	Access could not be confirmed: the API key is invalid, or the BuyersID does not match a customer account the key may access	Check the API key and BuyersID; ask BCF if both belong together
404	The requested feed resource was not available, or an error occurred while streaming the feed data	Check the endpoint address; retry once, then contact BCF
429	Too many requests in a short period	Wait the number of seconds in the Retry-After response header, then try again
500	The service encountered an unexpected problem	Retry later; if it continues, send the requestId to BCF support

Common validation errors (400)

Message	Cause and fix
BuyersID is required.	The BuyersID parameter is absent. Add it to the query string.
Invalid BuyersID format. Must be a valid UUID.	The BuyersID is not a valid UUID. Copy it completely, including hyphens, and remove spaces.
Invalid format parameter. Must be "json" or "csv".	Use only csv or json.
Invalid country code: ... Must be ISO 3166 alpha-2 (e.g., BE, NL, DE).	Use exactly two letters, such as BE.
Invalid language code. Must be ISO 639-1 (e.g., en, nl, fr).	Use exactly two letters, such as en.
Invalid currency code: ... Must be ISO 4217 (e.g., EUR, USD, GBP).	Use exactly three letters, such as EUR.
Invalid currency: prices for this customer are in EUR. ...	The requested currency differs from the currency of your price list. Omit the currency parameter or use your price list currency.

Authentication errors (401)

• An invalid API key is rejected before the feed is generated.
• Customer not found for the provided BuyersID. means the BuyersID does not match a known customer account. Check the UUID for typos, and confirm with BCF that the API key is authorised for this account.

Rate limit errors (429)

Rate limiting is applied per client IP: at most 100 requests per rolling minute. When the limit is exceeded, the response carries a Retry-After header with the number of seconds to wait. See Rate limits.

Reporting a problem

When asking for help, share:

• the date and time of the request,
• the request address with the BuyersID removed,
• the HTTP status code,
• the requestId from the error response.

Never share the API key.