<?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>API Design for C++</title>
	<atom:link href="http://www.apibook.com/blog/feed" rel="self" type="application/rss+xml" />
	<link>http://www.apibook.com/blog</link>
	<description>Resources for writing Application Programming Interfaces</description>
	<lastBuildDate>Thu, 09 May 2013 15:40:47 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>JavaScript API Design</title>
		<link>http://www.apibook.com/blog/archives/231</link>
		<comments>http://www.apibook.com/blog/archives/231#comments</comments>
		<pubDate>Thu, 28 Feb 2013 18:31:07 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Web APIs]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=231</guid>
		<description><![CDATA[Brandon Satrom has written a cool article on the secrets of awesome JavaScript API Design. While the focus is squarely on JavaScript, Brandon talks about the greater qualities of good API design and the need for developers to think about how other developers will use their code. http://webstandardssherpa.com/reviews/secrets-of-awesome-javascript-api-design/]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/231/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Government recommendations for Web API Design</title>
		<link>http://www.apibook.com/blog/archives/224</link>
		<comments>http://www.apibook.com/blog/archives/224#comments</comments>
		<pubDate>Mon, 03 Dec 2012 07:22:49 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Web APIs]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Web-Services]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=224</guid>
		<description><![CDATA[The US Federal government has published a set of guidelines for government agencies that want to design Web-based APIs. This includes recommendations on authentication, keys, documentation, and code samples; with links to examples of Web APIs in the .gov domain. http://www.howto.gov/mobile/api-design-documentation]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/224/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Java API Design Checklist</title>
		<link>http://www.apibook.com/blog/archives/223</link>
		<comments>http://www.apibook.com/blog/archives/223#comments</comments>
		<pubDate>Mon, 07 May 2012 04:20:55 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Process]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=223</guid>
		<description><![CDATA[Ferenc Mihaly maintains a blog call the Amiable API where he posts various articles on API design. As part of this blog, he provides a checklist of dos and don&#8217;t in API design. The list is focused on the Java programming language, however, most of what Ferenc presents it applicable to other languages too. I [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/223/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Richardson Maturity Model</title>
		<link>http://www.apibook.com/blog/archives/220</link>
		<comments>http://www.apibook.com/blog/archives/220#comments</comments>
		<pubDate>Tue, 24 Apr 2012 06:29:30 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Web APIs]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Web-Services]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=220</guid>
		<description><![CDATA[Martin Fowler wrote about a way to approach RESTful Web APIs developed by Leonard Richardson. This presents 4 successive levels of concepts, from the simple &#8220;plain old XML&#8221; layer, through the notion of resources, http verbs, and hypermedia controls. Martin does a great job of explaining each of the layers through the use of figures and [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/220/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>API Usability Testing at AT&amp;T</title>
		<link>http://www.apibook.com/blog/archives/219</link>
		<comments>http://www.apibook.com/blog/archives/219#comments</comments>
		<pubDate>Wed, 04 Apr 2012 16:46:15 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Testing]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=219</guid>
		<description><![CDATA[Pamela Fox wrote about some great process that AT&#38;T implemented to test the usability of their APIs. They invited several developers to come in and test out their APIs and give feedback on ways they can improve their developer experience. This is a great idea and fantastic way to improve an API based upon actual [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/219/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New eBook on Web API Design</title>
		<link>http://www.apibook.com/blog/archives/216</link>
		<comments>http://www.apibook.com/blog/archives/216#comments</comments>
		<pubDate>Fri, 23 Mar 2012 10:44:55 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Web APIs]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Versioning]]></category>
		<category><![CDATA[Web-Services]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=216</guid>
		<description><![CDATA[The folk at apigee have distilled everything they&#8217;ve learned about Web API design over the last few years into a new free eBook called &#8220;Web API Design: Crafting Interfaces that Developers Love.&#8221; This collates many of the details from their various blog posts into a single reference, covering topics such as REST, handling errors, versioning, [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/216/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>APIs: A Strategy Guide</title>
		<link>http://www.apibook.com/blog/archives/213</link>
		<comments>http://www.apibook.com/blog/archives/213#comments</comments>
		<pubDate>Wed, 21 Dec 2011 05:29:13 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Web APIs]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Web-Services]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=213</guid>
		<description><![CDATA[A new book on developing Web-based APIs is about to be published called &#8220;APIs: A Strategy Guide: Creating Channels with Application Programming Interfaces.&#8221; The book is written by Dan Jacobson, Greg Brail, and Dan Woods, who between them have an impressive background in developing real-world Web APIs. The book aims to educate executives and business development teams [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/213/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Versioning Tips for RESTful API Design</title>
		<link>http://www.apibook.com/blog/archives/212</link>
		<comments>http://www.apibook.com/blog/archives/212#comments</comments>
		<pubDate>Sun, 11 Dec 2011 19:16:05 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Web APIs]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Versioning]]></category>
		<category><![CDATA[Web-Services]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=212</guid>
		<description><![CDATA[Brian Mulloy at Apigee wrote a short article on versioning for Web APIs where he contrasts three different methods of including versioning information in a URL. These include using a timestamp or version number in the URL path, or accepting a version number as an optional parameter. Brian suggests using a mandatory version number as [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/212/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How API Testing Can Help</title>
		<link>http://www.apibook.com/blog/archives/210</link>
		<comments>http://www.apibook.com/blog/archives/210#comments</comments>
		<pubDate>Wed, 07 Dec 2011 06:48:32 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Testing]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=210</guid>
		<description><![CDATA[Bj Rollison wrote an article on API testing in which he talks about the differences between unit, API, and GUI testing. He goes on to describe some of the key benefits of API testing, including: reduced testing costs, improved productivity, and higher functional quality. Bj concludes by talking about the relationship between developers and testers. [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/210/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Books on REST Web APIs</title>
		<link>http://www.apibook.com/blog/archives/208</link>
		<comments>http://www.apibook.com/blog/archives/208#comments</comments>
		<pubDate>Sun, 06 Nov 2011 00:48:09 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Web APIs]]></category>
		<category><![CDATA[Books]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Web-Services]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=208</guid>
		<description><![CDATA[If you want to read something a little longer than a blog article on how to build REST Web APIs then there are a few books out there that may be of interest to you: REST API Design Rulebook Restful Web Services RESTful Web Services Cookbook REST in Practice]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/208/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>APIs Are For Human Beings</title>
		<link>http://www.apibook.com/blog/archives/205</link>
		<comments>http://www.apibook.com/blog/archives/205#comments</comments>
		<pubDate>Fri, 04 Nov 2011 16:32:33 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Web APIs]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Versioning]]></category>
		<category><![CDATA[Web-Services]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=205</guid>
		<description><![CDATA[In this Twilio Engineering blog article, Frank Stratton makes the point that computers don&#8217;t care about API design. APIs should be designed for human beings first and computers second. Using example Web APIs developed at Twilio, he talks about the need for having many eyes and minds see the design first, simplifying the surface area [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/205/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>API Design for Humans</title>
		<link>http://www.apibook.com/blog/archives/202</link>
		<comments>http://www.apibook.com/blog/archives/202#comments</comments>
		<pubDate>Mon, 03 Oct 2011 03:48:52 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Web-Services]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=202</guid>
		<description><![CDATA[Noah at 37 Signals wrote about API design for Web APIs. The key point he makes is about the need for strong documentation and having that documentation in an easy-to-search format. He then talks about authentication, advocating that an API offers multiple authentication schemes. Finally, he talks about building REST-like interfaces. http://37signals.com/svn/posts/3018-api-design-for-humans]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/202/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Amiable API</title>
		<link>http://www.apibook.com/blog/archives/200</link>
		<comments>http://www.apibook.com/blog/archives/200#comments</comments>
		<pubDate>Fri, 23 Sep 2011 03:50:45 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=200</guid>
		<description><![CDATA[Ferenc Mihaly has created a blog called The Amiable API dedicated to designing developer-friendly APIs. This web site grew out of a set of internal guidelines that Ferenc produced for his company and ultimately decided to publish in a blog format. Some of his recent posts include: Choosing memorable names, Striving for consistency, Keeping it simple, Considering the perspective of the caller, [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/200/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>API Design Done Right</title>
		<link>http://www.apibook.com/blog/archives/196</link>
		<comments>http://www.apibook.com/blog/archives/196#comments</comments>
		<pubDate>Mon, 19 Sep 2011 02:42:05 +0000</pubDate>
		<dc:creator>martin</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[C/C++]]></category>
		<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://www.apibook.com/blog/?p=196</guid>
		<description><![CDATA[Finish software house Reaktor has published some slides on how to design good APIs. The authors, Jari Mäkelä and Ville Peurala, make the point that bad APIs can infect client code and lead to bad client code too. They state that some elements of good design include being intuitive, easy to learn from simple examples, self explanatory, and [...]]]></description>
		<wfw:commentRss>http://www.apibook.com/blog/archives/196/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
