In recent months, the number of government open data APIs has been increasing rapidly due to a variety of factors including the development of open data technology platforms, the launch of Project Open Data and a recent White House executive order regarding government data. This post is a general overview of several recent factors that have led to the rise of government open data APIs.
Skype is closing its desktop API at the end of 2013. Stormpath joins the AWS marketplace and partner network. Plus: a hack-day tool for parsing civic data and 13 new APIs.
This past week 6 new mashups were added to our mashup directory and 11 different APIs were used to build them. Some of the newer or less frequently seen APIs include IMSAS, Juno Download and Mobile Phone Megastore. The most often used APIs this week are eBay Finding, IMSAS and Twitter. And the most commonly used types of APIs were Music (5 APIs, 5 mashups), Shopping (1 APIs, 1 mashups) and Social (1 APIs, 1 mashups). The list below shows which APIs were used by which mashups:
This week we had 49 new APIs added to our API directory including a movement activity tracking application, online calendar service, cloud-based MySQL database, RSS reader service and image recognition service. We also covered an API to help keep crowdfunding safe and how to increase engagement with the Newsweaver API. Below are more details on each of these new APIs.
Our API directory now includes 95 sharing APIs. The newest is the Screenhero API. The most popular, in terms of mashups, is the Zillow API. We list 79 Box.net mashups. Below you’ll find some more stats from the directory, including the entire list of sharing APIs.
Digital Public Library Launch. Google Glass API could be foggy. Plus: Disrupt NY Hackathon, the new open world of banking, and 20 new APIs.
Facebook provides API to manage comment threads. Google SMS and voice integration. Plus: Gnip adds six new social data sources available via Public API and advertising and In-App Messaging APIs added to the AT&T API Platform.
APIs enable incredible customization. No longer are customers locked into a specific interface or feature set: they can modify and augment core functionality as they see fit. It is incredibly liberating, but just deploying any old API isn’t enough. You need to really understand how people use your API. Luckily, you can group most API usage into one of two buckets: reading and writing.