Fork me on GitHub

I've been tracking on what I call API aggregation for some time now. I started seeing the API aggregation trends in 2010, then I saw this pick up in 2011 with the emergence of providers like Singly and Adigami.

While many new companies provide you with interoperability and automation between multiple APIs, I consider aggregators to be about bringing together multiple APIs into a single aggregated end-point for developers to use, then also providing potentially new APIs that are only possible, because of the aggregation.

Last year, after I started spending more time in Washington DC, I met a talented group of folks who were playing around with the idea of an aggregate API for federal government. In the last couple weeks it looks like they were serious about it, and launched the debut version of Fed{API}.

Fed{API} is looking to make government data more accessible and reusable by taking data from multiple sources, some easy to pull and some much more difficult, then collect, correlate and catalog into a single, aggregate API stack that developers can put to use.

I'm a big fan of API Aggregation. I think this is the future of standardizing APIs and data across many sources, but as I'm watching providers tackle this, you begin to realize what a massive undertaking it will be. And FedAPI is looking to do this by opening up federal government data, which by itself is a massive challenge. So FedAPI is tackling two pretty massive problems, as a core business model.

Even with the massive challenge ahead, I will be supporting FedAPI 100%, and doing what I can to make sure their initiative is successful. To do so, I think they will have to get two other groups involved:

  • Other API Aggregate Providers - FedAPI needs to make sure and reach out to Singly, Temboo, Adigami and the other API aggregators and see what they can learn, share knowledge and wisdom. Aside from FedAPI, all these providers need to work together and not re-invent the wheel when it comes to Auth and API connectors
  • Public At Large - FedAPI has to introduce tools that allow figure everyday Joe and Jane citizen into the equation. Some users are going to be very knowledgable and passionate about specific areas, and there has to be ways to share the load and let them help clean and verify data, and other meaningful tasks

I don't think that API Aggregation is the answer to all the problems that plague API integration, but I think API aggregators will play a major role in helping standardize API interfaces, data formats and provide critical cross-provider, inter-agency knowledge and wisdom--something individual API providers may never be able to deliver alone.

One thing I want to lend a hand with, when it comes to FedAPI, is help create the blueprint of which federal agencies already have APIs and open data sets, and where these exists. I can also be the aggregator of news, analysis and best practices across the federal API landscape.

I'm on board FedAPI, let's make this happen.




comments powered by Disqus
Google+