{"API Evangelist"}

Which API Service Providers Across The 20 Areas I Track On Have APIs?

As I go through each of the 20 core areas of the API sector that I am keeping an eye on, in preparation for my keynotes at @DefragCon and @APIStrat, I'm taking a fresh look at which of them have APIs. When you think about it, if a company is selling a product or service to API providers, encouraging an API focus--they should probably have APIs. :-)

As I was updating some of the news, companies, and reviewing the common building blocks I have aggregated across the 20 areas of research, I just poked my head around to see if I could find an API for each service provider. There are many things that look like a language specific API, but I am looking for a clear developer / API area, with a coherent web API available, as we'd expect from API providers in 2015.

After spending a couple hours looking through my core research, I found the following service providers, in the follow areas, actually had web APIs available:

This was my first pass through all of my core research looking for APIs, so I am sure I missed some--let me know which ones I missed. My design, hypermedia, performance, monetization, evangelism, embeddable, client, SDK, visualization, and virtualization didn't have any clear leaders who had easy to find APIs. I will update as I find them--which smells like an opportunity to me.

Eventually I'd like to see some common definitions to be established across all these areas of the API space, but as you can see, like the rest of the API space, there is a lot of work to be done. Now that I have a list of API service providers who have APIs, I can start crafting, and aggregating API definitions for all the APIs. Once i've done this I can start looking for the overlap across them, and see if I can highlight the common patterns, and establish some bridges for the differences between them.

Every potential stage of the API life-cycle will have to be automated in the future, and ironically APIs will be how we do that.