<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Sailthru Blog &#187; API</title>
	<atom:link href="http://blog.sailthru.com/category/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sailthru.com</link>
	<description>All email, all the time</description>
	<lastBuildDate>Mon, 19 Dec 2011 22:12:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>API HTTP Error Codes</title>
		<link>http://blog.sailthru.com/api/api-http-error-codes/</link>
		<comments>http://blog.sailthru.com/api/api-http-error-codes/#comments</comments>
		<pubDate>Thu, 12 May 2011 18:15:40 +0000</pubDate>
		<dc:creator>Ian White</dc:creator>
				<category><![CDATA[API]]></category>
		<category><![CDATA[Tech]]></category>

		<guid isPermaLink="false">http://blog.sailthru.com/?p=626</guid>
		<description><![CDATA[For a while, our API wasn&#8217;t as RESTful as it could be. That&#8217;s because we didn&#8217;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 [...]]]></description>
			<content:encoded><![CDATA[<p>For a while, our API wasn&#8217;t as <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer">RESTful</a> as it could be. That&#8217;s because we didn&#8217;t make use of HTTP header codes.</p>
<p>Unless the API was truly down, we would always return 200 OK, and use a <a href="http://docs.sailthru.com/api/errors">Sailthru Error Code</a> to denote the exact type of error.</p>
<p>After reviewing our existing client libraries to make sure this change would be a non-breaking change, we&#8217;ve added <a href="http://docs.sailthru.com/api/http-response-codes-and-errors">proper HTTP response codes</a> on errors. This gives you a broader, more general insight into what&#8217;s wrong, and will work well with general HTTP transport mechanisms.</p>
<p>For example, if you try to send to a template that doesn&#8217;t exist, you&#8217;ll continue to get a Sailthru error 14 (&#8220;Unknown template&#8221;) in the body of the returned response, but you&#8217;ll also receive a 404 Not Found in the header of the HTTP request.</p>
<p>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.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.sailthru.com/api/api-http-error-codes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Paradise by the Dashboard</title>
		<link>http://blog.sailthru.com/reporting/paradise-by-the-dashboard/</link>
		<comments>http://blog.sailthru.com/reporting/paradise-by-the-dashboard/#comments</comments>
		<pubDate>Mon, 04 Oct 2010 20:51:01 +0000</pubDate>
		<dc:creator>noah</dc:creator>
				<category><![CDATA[API]]></category>
		<category><![CDATA[Reporting]]></category>
		<category><![CDATA[dashboard]]></category>
		<category><![CDATA[engagement]]></category>
		<category><![CDATA[graphs]]></category>
		<category><![CDATA[metrics]]></category>

		<guid isPermaLink="false">http://blog.sailthru.com/?p=241</guid>
		<description><![CDATA[As part of the ongoing redesign of our user interface, we&#8217;ve just rolled out a new dashboard feature. Now, when you sign in to your Sailthru account you&#8217;ll be presented with selected metrics that provide a clear and quickly digestible window into your account performance. In the example pictured above you&#8217;ll notice charts displaying list [...]]]></description>
			<content:encoded><![CDATA[<p>As part of the ongoing redesign of our user interface, we&#8217;ve just rolled out a new dashboard feature. Now, when you sign in to your Sailthru account you&#8217;ll be presented with selected metrics that provide a clear and quickly digestible window into your account performance.</p>
<div id="attachment_298" class="wp-caption aligncenter" style="width: 305px"><a rel="attachment wp-att-298" href="http://blog.sailthru.com/reporting/paradise-by-the-dashboard/attachment/dashboard/"><img class="size-medium wp-image-298" title="Dashboard" src="http://blog.sailthru.com/wp-content/uploads/2010/10/Dashboard-295x300.png" alt="" width="295" height="300" /></a><p class="wp-caption-text">Ain&#39;t no doubt about it. Baby, got to go out and shout it!</p></div>
<p>In the example pictured above you&#8217;ll notice charts displaying list member growth and engagement, mass and transactional send rates as well as campaign results.  The graphs on the left are customizable, allowing you to select durations from one day up to the entirety of your account history. On the right side of the dashboard is a pie graph depicting member activity by engagement as well as ledgers showing recent campaign results and scheduled campaigns.  (For more information on understanding engagment see <a href="http://docs.sailthru.com/engagement">engagement tags</a>.)  For clients who only send transactional emails the dashboard will default to a display which shows only those applicable email metrics.</p>
<p>To navigate back to the dashboard from elsewhere in the site, just click on the Sailthru logo and, bam! you&#8217;re back.  We hope you&#8217;ll find the new dashboard useful, but this is just the first step: in the coming weeks we&#8217;ll be adding more functionality to the dashboard, as well as making it more customizable and deeply drillable.  We&#8217;re working hard to make our interface as intuitive, informative and revealing as possible, and we would love to hear what you think.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.sailthru.com/reporting/paradise-by-the-dashboard/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>&#8220;text only&#8221; test send</title>
		<link>http://blog.sailthru.com/api/text-only-test-send/</link>
		<comments>http://blog.sailthru.com/api/text-only-test-send/#comments</comments>
		<pubDate>Fri, 23 Jul 2010 18:29:03 +0000</pubDate>
		<dc:creator>noah</dc:creator>
				<category><![CDATA[API]]></category>

		<guid isPermaLink="false">http://blog.sailthru.com/?p=134</guid>
		<description><![CDATA[For clients who want to preview how their emails will be rendered by text only email clients our &#8220;text only&#8221; feature allows them to test send text only versions of their emails.  When editing a campaign or template, simply select the &#8220;text only&#8221; box and test send to the emails of your choosing. Now try [...]]]></description>
			<content:encoded><![CDATA[<p>For clients who want to preview how their emails will be rendered by text only email clients our &#8220;text only&#8221; feature allows them to test send text only versions of their emails.  When editing a campaign or template, simply select the &#8220;text only&#8221; box and test send to the emails of your choosing.</p>
<p style="text-align: center;">
<p style="text-align: center;">
<p style="text-align: center;"><a rel="attachment wp-att-143" href="http://blog.sailthru.com/api/text-only-test-send/attachment/picture-34-2/" target="_blank"><img class="aligncenter size-full wp-image-143" title="Text only feature" src="http://blog.sailthru.com/wp-content/uploads/2010/07/Picture-341.png" alt="" width="692" height="181" /></a></p>
<p>Now try and say &#8220;test send text only&#8221; five times fast.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.sailthru.com/api/text-only-test-send/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>API Library updates</title>
		<link>http://blog.sailthru.com/api/api-library-updates/</link>
		<comments>http://blog.sailthru.com/api/api-library-updates/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 19:08:04 +0000</pubDate>
		<dc:creator>Neil Capel</dc:creator>
				<category><![CDATA[API]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[asp.net]]></category>
		<category><![CDATA[email integration]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[sailthru API]]></category>

		<guid isPermaLink="false">http://blog.sailthru.com/wordpress/?p=20</guid>
		<description><![CDATA[To make intergrating us a simple as possible we&#8217;ve added libraries to work with our API. Current approved libraries include: PHP 5 Ruby ASP.net We also have the following in beta release (send us an email to get a hold of them): Python Java We&#8217;d love a PERL version too so if you want free [...]]]></description>
			<content:encoded><![CDATA[<p>To make intergrating us a simple as possible we&#8217;ve added libraries to work with our API.</p>
<p>Current approved libraries include:</p>
<ul>
<li><a title="PHP Library for sailthru API's" href="http://sailthru.com/admin/api?view=php5">PHP 5</a></li>
<li><a title="Ruby library for sailthru api" href="http://sailthru.com/admin/api?view=ruby">Ruby</a></li>
<li><a title="ASP.net sailthru API integration" href="http://sailthru.com/admin/api?download=aspnet">ASP.net</a></li>
</ul>
<p>We also have the following in beta release (send us an email to get a hold of them):</p>
<ul>
<li>Python</li>
<li>Java</li>
</ul>
<p>We&#8217;d love a PERL version too so if you want free service for a month please provide the PERL library!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.sailthru.com/api/api-library-updates/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

