In the platform you can use API integrations or Webhooks to transfer data from a playable campaign to a CRM or ESP system.
When integrating with an ESP or CRM system, information from the platform is transferred, processed, and feedback is returned back. The API will return a log, including a HTTP code, that indicates the status of the API call.
Overview of status codes (and how to fix them)
The HTTP status code from the log will most likely fall within one of the following categories:
2xx successful: This class of status codes indicates the action requested by the client was received, understood, and accepted. The browser has received the expected information, and the data was successfully transferred.
4xx client error: This class of status code is intended for situations in which the error seems to have been caused by the client. Most common reason for this error is that the website or the page could not be reached, either the page is unavailable or the request contains bad syntax.
5xx server error: 5xx status codes suggest a server issue. If you receive a 5xx error, we recommend checking with your service provider to see if they are experiencing any system-wide issues.
The table below provides some examples of status and error codes. The list is not exhaustive, and the codes can vary, depending on what API integration you are using.
HTTP Status Code examples
Class 200 | Class 400 | Class 500 |
200 OK 201 Created 202 Accepted | 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 409 Conflict | 500 Internal Server Error 501 Not Implemented 503 Service Unavailable 504 Gateway Timeout 599 Network Connect Timeout Error |
Most API integrations offer a more extensive error glossary on their website or in their documentation. It can be helpful to look to these for more context that can help you troubleshoot on the error.
Finding the ESP or CRM logs
In the platform you will find information on ESP or CRM logs under each registration. This goes for both successful and unsuccessful transfers:
When data is successfully transferred, the log will include only a status code:
If anything goes wrong with your API calls, the API will most of the time return an error type and brief explanation of when the error is triggered. The image below shows an error code and possible explanation for the failed data transfer.
The image above shows an error code 422, which means "unprocessable content". Looking further into the error message, we can deduce that the email we've attempted to send through the API is not recognized as valid, and that the character-set expected is "UTF-8".
With this information, we now know to double check the content of the email address being sent through, which in this case was: "calebæhnson@provider.com". The character "æ" is not part of the UTF-8 character-set and as such, we are trying to send an invalid value through the API.
Sometimes, the cause of an error can be derived from the description, while other times, it may be a bit more challenging to interpret the error code. You are always welcome to reach out to our chat support team if you need help troubleshooting on your API integration and error logs.