<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Purity Networks Blog &#187; api</title>
	<atom:link href="http://www.purity.net/blog/tag/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.purity.net/blog</link>
	<description>Corporate blog for Purity Networks</description>
	<lastBuildDate>Sun, 25 Jul 2010 19:35:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<!-- podcast_generator="podPress/8.8" - maintenance_release="8.8.4" -->
		<copyright>2006-2008 </copyright>
		<managingEditor>groberts@interjuncture.com (Purity Networks Blog)</managingEditor>
		<webMaster>groberts@interjuncture.com (Purity Networks Blog)</webMaster>
		<category>posts</category>
		<ttl>1440</ttl>
<br />
<b>Warning</b>:  htmlentities() expects at most 3 parameters, 4 given in <b>/home/purity/httpdocs/blog/wp-content/plugins/podpress/podpress_feed_functions.php</b> on line <b>31</b><br />
		<itunes:keywords></itunes:keywords>
<br />
<b>Warning</b>:  htmlentities() expects at most 3 parameters, 4 given in <b>/home/purity/httpdocs/blog/wp-content/plugins/podpress/podpress_feed_functions.php</b> on line <b>31</b><br />
		<itunes:subtitle></itunes:subtitle>
<br />
<b>Warning</b>:  htmlentities() expects at most 3 parameters, 4 given in <b>/home/purity/httpdocs/blog/wp-content/plugins/podpress/podpress_feed_functions.php</b> on line <b>31</b><br />
		<itunes:summary></itunes:summary>
		<itunes:author>Purity Networks Blog</itunes:author>
		<itunes:category text="Society &amp; Culture"/>
		<itunes:owner>
			<itunes:name>Purity Networks Blog</itunes:name>
			<itunes:email>groberts@interjuncture.com</itunes:email>
		</itunes:owner>
		<itunes:block>No</itunes:block>
		<itunes:explicit>no</itunes:explicit>
		<itunes:image href="http://www.easyantispam.com/blog/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" />
		<image>
			<url>http://www.easyantispam.com/blog/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url>
			<title>Purity Networks Blog</title>
			<link>http://www.purity.net/blog</link>
			<width>144</width>
			<height>144</height>
		</image>
		<item>
		<title>Purity Networks API version 2.0 documentation started</title>
		<link>http://www.purity.net/blog/2009/12/02/purity-networks-api-version-2-0-documentation-started/</link>
		<comments>http://www.purity.net/blog/2009/12/02/purity-networks-api-version-2-0-documentation-started/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 18:29:05 +0000</pubDate>
		<dc:creator>George Roberts</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[new-features]]></category>

		<guid isPermaLink="false">http://www.purity.net/blog/2009/12/02/purity-networks-api-version-2-0-documentation-started/</guid>
		<description><![CDATA[With the release of UserProtect, we’re working on a new version of the Purity Networks API to incorporate functionality to work with UserProtect and DomainProtect accounts.  We’re still in the early design and development stage, but we’ve started working on the documentation on the Wiki at the same time to give our users input into [...]]]></description>
		<wfw:commentRss>http://www.purity.net/blog/2009/12/02/purity-networks-api-version-2-0-documentation-started/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UserProtect service now available</title>
		<link>http://www.purity.net/blog/2009/11/23/userprotect-service-now-available/</link>
		<comments>http://www.purity.net/blog/2009/11/23/userprotect-service-now-available/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 02:06:46 +0000</pubDate>
		<dc:creator>George Roberts</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[new-features]]></category>
		<category><![CDATA[news]]></category>
		<category><![CDATA[UserProtect]]></category>

		<guid isPermaLink="false">http://www.purity.net/blog/?p=224</guid>
		<description><![CDATA[We&#8217;re happy to announce that our new UserProtect service is now available for ordering! See our services page for detailed information. We&#8217;re working on a new version of our API that will include UserProtect functionality, but at the moment it&#8217;s not available yet.  We&#8217;re hoping to have this available for use in the next couple [...]]]></description>
		<wfw:commentRss>http://www.purity.net/blog/2009/11/23/userprotect-service-now-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>API Documentation Available</title>
		<link>http://www.purity.net/blog/2008/06/22/api-documentation-available/</link>
		<comments>http://www.purity.net/blog/2008/06/22/api-documentation-available/#comments</comments>
		<pubDate>Sun, 22 Jun 2008 07:18:24 +0000</pubDate>
		<dc:creator>George Roberts</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[api]]></category>

		<guid isPermaLink="false">http://www.easyantispam.com/blog/?p=93</guid>
		<description><![CDATA[We&#8217;ve started putting together the Easy Antispam API documentation in Wiki form.  We still have a number of functions to describe in the documentation, but that will be done within the next couple of days. Feel free to start taking a look around the documentation and getting a feel for the API.  There is an [...]]]></description>
		<wfw:commentRss>http://www.purity.net/blog/2008/06/22/api-documentation-available/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>API Ready for Testers</title>
		<link>http://www.purity.net/blog/2008/06/19/api-ready-for-testers/</link>
		<comments>http://www.purity.net/blog/2008/06/19/api-ready-for-testers/#comments</comments>
		<pubDate>Fri, 20 Jun 2008 05:18:20 +0000</pubDate>
		<dc:creator>George Roberts</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[api]]></category>

		<guid isPermaLink="false">http://www.easyantispam.com/blog/?p=92</guid>
		<description><![CDATA[We&#8217;re ready for a few testers to give the API some work and give us some feedback on it. We have the following functions done: listDomains Lists domains assigned to the specified server addDomain Adds a domain to the specified server addDomainAlias Adds an alias domain to the specified domain deleteDomain Deletes the specified domain [...]]]></description>
		<wfw:commentRss>http://www.purity.net/blog/2008/06/19/api-ready-for-testers/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Account Manager API &#8211; What features are needed?</title>
		<link>http://www.purity.net/blog/2008/06/17/account-manager-api-what-features-are-needed/</link>
		<comments>http://www.purity.net/blog/2008/06/17/account-manager-api-what-features-are-needed/#comments</comments>
		<pubDate>Tue, 17 Jun 2008 07:46:29 +0000</pubDate>
		<dc:creator>George Roberts</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[api]]></category>

		<guid isPermaLink="false">http://www.easyantispam.com/blog/?p=91</guid>
		<description><![CDATA[Hi everyone, We&#8217;ve been doing some work on the Account Manager API and I&#8217;d like some feedback on what everyone feels they need as far as functionality in the API.  First, let me say that at this time we&#8217;re only planning on implementing an API for ServerProtect accounts.  We may add some DomainProtect functionality at [...]]]></description>
		<wfw:commentRss>http://www.purity.net/blog/2008/06/17/account-manager-api-what-features-are-needed/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
