{"API Evangelist"}

Gearing Up For Enterprise Sales With An API Service Level Agreement

I am working through the AWS APIs and the Google APIs, and profiling the building blocks across both of these API operations. My objective in doing this work is to learn as much as I possibly can about how these companies are doing APIs. After diving into Google's APIs I noticed that they were slightly more ahead of the curve when it comes to providing server level agreements (SLA) for their cloud APIs, than AWS.

I noticed nine while working through Google APIs:

I noticed five SLAs while working through AWS APIs:

I am sure there are other dedicated SLA pages I'm missing, as well as SLAs embedded in the documentation and terms of service of systems. From what I can tell, these dedicated SLAs for APIs are in response to a shift in the landscape to sell more services to the enterprise, requiring that these details of doing business move front and center. With the volatility often associate with APIs in recent years, I'm guessing an API SLAs will continue to become an essential element in all API integration decisions in coming years.

There has been enough movement in the area of API service level agreements for me to consider adding a dedicated research area to my work. I've written about the SLA APIs I've stumbled across, and seeing SLAs float to the top with the bigcos, so it makes sense to pay closer attention to what is happening. Eventually, I'll aggregate the common building blocks across the API SLAs I'm finding, and the other more unique approaches to ensuring API reliability and stability when doing business online today.