API HTTP Error Codes

For a while, our API wasn’t as RESTful as it could be. That’s because we didn’t make use of HTTP header codes.

Unless the API was truly down, we would always return 200 OK, and use a Sailthru Error Code to denote the exact type of error.

After reviewing our existing client libraries to make sure this change would be a non-breaking change, we’ve added proper HTTP response codes on errors. This gives you a broader, more general insight into what’s wrong, and will work well with general HTTP transport mechanisms.

For example, if you try to send to a template that doesn’t exist, you’ll continue to get a Sailthru error 14 (“Unknown template”) in the body of the returned response, but you’ll also receive a 404 Not Found in the header of the HTTP request.

We hope this helps our easy-to-integrate API get that much easier. If you have any questions or comments, feel free to email us any time.

2018 DATA PRIVACY REPORT:

What Brands Need to Know About Consumer Attitudes Post-Cambridge Analytica