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
- Showcasing Your API Integrations With Other Platforms
- Increasing The Focus On APIs In Higher Education Is Important
- Getting To Know Mike Amundsen For The API Craft 2014 Detroit Hypermedia Panel
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Models For API Driven Startups Built Around Public Data
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons