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.
Publishing in a Cookieless World: How First-Party Data Is Transforming Media Companies
Third-party cookies have made it easy for media companies to reach subscribers. But by 2022, Google will say goodbye to them forever. Find out why you need first-party data moving forward.
Personalization vs. Segmentation: The Real Difference and Why it Matters
Personalization is many things to many marketers. For some, it’s a business strategy that increases customer lifetime value and paves the way for profitable,...
How Personalization Can Enhance Email for Publishers
Email for publishers is having a moment in the sun. Throughout the coronavirus pandemic, subscriptions have been on the rise and it’s been paying...