This article will cover API errors that you can receive from our Bloomreach Engagement API endpoints and their particular meanings
|
Code |
Error | Message |
|---|---|---|
| 401 Unauthorized | Access key not found | Happens when the API key is invalid or is not tied to the secret key that you specified |
| 403 Forbidden | invalid secret | It is related to the incorrect secret key used in the authorization |
| 404 Not Found | The requested URL was not found on the server | If you entered the URL manually, please check your spelling and try again |
| 400 Bad Request | Invalid JSON | The JSON structure of the payload is corrupted, to solve this problem, we recommend running the payload through a JSON validator and identifying what is breaking the valid JSON |
| 400 Bad Request | Missing params: Param1, Param2 | Params defined in the TX email template are missing in the payload that you are sending over to the API endpoint |
| 400 Bad Request | Fields [<field name>, <field name>] are not properly defined | You cannot update non-existing item properties when calling an update catalog API endpoint, the fields must be already defined in the catalog |
| 200 OK | At least one valid id should be specified | A valid ID must contain at least one alphanumeric character and cannot be 'null' or 'undefined' |
| 200 OK | Not authorized to add event of specified type | Indicates missing permission in the Project settings → API. You must set a specific permission to be able to add a particular event |
| 404 Not Found | Customer does not exist | Is present when trying to export a non-existent customer from the project, make sure that the customer ID you specified is present in the project |
| 403 Forbidden | No permission to export customer | Check Project settings → API → GDPR → Export customer. Trying to export a customer profile while the GDPR permissions for exporting a customer are not granted for this API group |
| 200 OK | Failed to prepare personalization for template | Is related to transactional email API and indicates a problem with the JINJA code where some part was not able to execute properly, you need to debug the JINJA code within the template that you are trying to send |
| 400 Bad Request | Could not parse <id of the object> | Should be object id. Is related to TX email API and happens when you specify a nonexistent integration ID, please double check if the integration ID is present within the project token where you are making the request |
| 400 Bad Request | Template <id of the object> not found | Related to TX email API and happens when you specify a non-existing email template ID into the payload |
| N/A | CORS errors | You cannot make an API call to our endpoint through the front end, our endpoints only accept calls from the backend |