<?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>Micro Visions Blog &#187; api</title>
	<atom:link href="http://microvisionsinc.com/blog/tag/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://microvisionsinc.com/blog</link>
	<description>Technology news and updates blog from (and sometimes about) your friendly neighborhood IT service provider; Micro Visions, Inc.</description>
	<lastBuildDate>Fri, 10 Sep 2010 19:53:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A Tale of Two APIs</title>
		<link>http://microvisionsinc.com/blog/2010/02/a-tale-of-two-apis/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=a-tale-of-two-apis</link>
		<comments>http://microvisionsinc.com/blog/2010/02/a-tale-of-two-apis/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 19:18:27 +0000</pubDate>
		<dc:creator>Randy</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[api]]></category>

		<guid isPermaLink="false">http://microvisionsinc.com/blog/?p=159</guid>
		<description><![CDATA[At Micro Visions, we are continually exposed to various application programming interfaces (APIs) in order to bridge client applications to existing codebases around the web. APIs are nothing more than libraries of code, exposed publicly by a company, for someone else to hook their code into. APIs give developers access to external data like stock [...]]]></description>
			<content:encoded><![CDATA[<p>At Micro Visions, we are continually exposed to various application programming interfaces (APIs) in order to bridge client applications to existing codebases around the web. APIs are nothing more than libraries of code, exposed publicly by a company, for someone else to hook their code into. APIs give developers access to external data like stock quotes, flight data, subscription lists and news.</p>
<p>One of the best APIs we have had the pleasure of using belongs to <a href="http://campaignmonitor.com" target="_blank">Campaign Monitor</a>. Campaign Monitor (CM) is a web service where clients can manage their email lists. We have developed applications that bridge our own client&#8217;s applications with services provided by CM. The service is top notch and their <a href="http://www.campaignmonitor.com/api/" target="_blank">API</a> is a joy to work with.</p>
<p>We&#8217;ve also worked with PayPal&#8217;s API. PayPal offers a wealth of developer documentation at <a href="http://x.com" target="_blank">x.com</a>. Unfortunately, the documentation is inconsistent as you travel between the official documents, the online documents, the support forums and the unofficial forums (where many of the answers are found of course). I <a href="http://randallhook.com/post/2010/02/04/Keys-to-Configuring-the-PayPal-Sandbox-for-Recurring-Payments.aspx" target="_blank">posted an article</a> to specifically address some of the hurdles you will encounter in configuring Recurring Payments (subscriptions) for PayPal&#8217;s Website Payments Pro plan.</p>
<p>Companies offering their own APIs would do well following Campaign Monitor&#8217;s example. Solid code and solid documentation make them an easy referral for future clients.</p>
]]></content:encoded>
			<wfw:commentRss>http://microvisionsinc.com/blog/2010/02/a-tale-of-two-apis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
