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.
2023 U.S. Consumer Trends Index Infographic
3 Interactive Experiences We Love Right Now
Interactive digital experiences can help build brand loyalty while delivering key details about your customer’s interests and future purchase intent. The importance of data...
Do You Need to Worry About Google’s Plan to Delete Inactive Accounts?
Marketers should use Google’s latest initiative as an opportunity to focus on their own data health and list quality. Last week Google announced that...
Data & AI
Thanksgiving Week Shows Retailers Collecting Zero-Party Data While Loyalty Programs Continue To Provide Solid Revenue Streams
The 2022 holiday shopping season has begun and forward-thinking brands are seizing the opportunity to collect zero-party data via interactive experiences in the busiest...