Posted on 08-22-2014
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
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Thank You @3Scale For Investing In The Community With @APIStrat
- Introducing API.Report, A Community API News Site
- Extract Knowledge From Audio And Video Using The Clarify API
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API