Posted on 06-02-2012
I’m excited about Barack Obama directing all federal agencies to have an API. The President has given federal agencies 90 days to create a page on its website, located at www.[agency].gov/digitalstrategy, to publicly report progress in meeting the requirements of the Strategy in a machine-readable format, and implement the requirements of the Strategy within 12 months.
As I said in my post, I wanted to setup a page to monitor this activity. I found a dataset of federal executive branch Internet domains, thanks to Anthony Sutardja, one of my readers. In the dataset there are 1467 domains, with 106 distinct agencies running those domains. The President states "executive department and agencies" in his directive. I can’t imagine we are going to see digital strategies in 90 days for all 1467 domains? I’m assuming it will occur within the top level agencies first. But I’m very curious see which agency domains follow, so I’m going to leave all of them up.
I created a script that will poll www.[agency].gov/digitalstrategy for each agency. I will run this every night this year. The script checks the HTTP status code for the page, records it with a time stamp, and the we’ll see who returns HTTP status code 200(OK) first. Quick note: It’s interesting to see which agency doesn’t properly use status codes, but that is another issue.
Anyone want to wager on who is first, and how many of the 1467 meet the requirements for posting their strategy and ultimately implementing APIs? Personally I’m hoping for CIA and the NSF. Think of the mashups you could make!!!
I all seriousness, this is extremely important. If agencies meet these requirements, we can see a radically different federal government in the coming years. As one of my readers and friend said on the post yesterday, "It looks like the Jeff Bezos mandate that he did 10 years ago!". If you don’t known what I’m talking about, read "The Secret to Amazons Success Internal APIs”.
You can visit the Federal Agency API Deployment Tracker page for more detail, I will keep the link prominent in the right hand feature area of this site, for the rest of the year.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- 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
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems
- APIs That Do One Thing And Do It Well Like ZipLocate
- Which API Do I Need?
- The Expanding API Conference Landscape
- Ocotoparts Open Source Google Spreadsheet