Fork me on GitHub

The other night I was writing about the need for a social media directory API, like the one the GSA has launched for the federal government, but specifically for the City of Chicago. I was trying to get a list of each of the City of Chicago Twitter accounts, and while I’m glad there is a central social media account list, I always want an API so I can eliminate the need for data entry.

After I posted my story, Oliver Seiler (@0seiler) emailed me the API endpoint for the New Zealand Government Directory API, which doesn't include the social media information that our federal government social media directory API delivers, but offers another look at what one possible pattern for government directory APIs is.

This is one of the by-products of my profiling of federal government APIs, that I will begin to see API patterns that ALL government possess, things like a directory API. There should be a WordPress of the government directory API, a open source PHP Web API, possessing a common API definition, allowing any government agency, of any level, to be able to quickly download and deploy a directory API for their branch of government.

I’m hoping when I’m done with my profiling of 120 federal government APIs, I'll have better suggestions of which APIs patterns government agencies should be offering by default. I will also have API definitions for all of these government API patterns, which I can probably pretty quickly crank out server side API code to support—who knows maybe Wordpress 4.1 will be available by then and I can use Wordpress as an API deployment framework.

Until then I will just start tracking on all the common patterns for government API deployment, and publish as stories her on API Evangelist, and on my federal government research site. I'm thinking other things I'm tracking on, like API deployment using containers, and deployment via PaaS platforms like Heroku, will contribute to this type of API deployment across government as well, making it a very interesting time to be in tech.




comments powered by Disqus
Google+