API HTTP Error Codes
May 12, 2011
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.
Build an Email Newsletter Everybody Loves
3 First-Party Data Tactics to Make Your Emails Better
Right now, successful email marketing is all about personalization. The good news is, you already know what buyers want — it’s right there in...
How Sailthru Used Virtual Events to Stay Close to its Customers
Like many brands, Sailthru was eager to get back to hosting live events in 2021. But instead the team encountered a year of last-minute...