There’s a certain breed of developer that has been talking about the benefits APIs can offer for many years now. In fact, if you’re reading this article, it’s likely that you’re one of them!
But it’s only in recent years, in part thanks to the rise of consumer facing services like IFTTT and Zapier, that more and more people have come around to this point of view. Read more
APIs are nothing new. Salesforce and eBay first allowed access to their web APIs in the year 2000, and other organizations were tinkering with the idea of exposing endpoints even before that.
The past few years, however, have seen such explosive growth that the API space is evolving more rapidly than ever before. Read more
According to The State of API Survey Report 2016 by Smartbear, nearly 85% of the respondents agree that API quality is crucial to their organization. The same survey identifies the top three reasons keeping organizations from delivering quality APIs are:
1) Increased demands for speed
2) Lack of integration between tools and systems
3) Managing expectations of different stakeholders
A remedy for the first reason can be found by fine-tuning architecture and optimizing code. Read more
In 2015 “there’s an API for that” became an oft-repeated phrase, entering the vernacular with the same frequency as the app-based equivalent. Fueling the usage of this phrase is an increasing number of organizations taking their products to market using a SaaS-first (Software-as-a-Service) approach, exposing an Application Programming Interface or API at the core of their offering. Read more
A top concern for treating your API as a product is creating a profitable business model. However, on the face of it, immediately charging people to use an API might seem like a strange thing to do, as adding a barrier to entry isn’t always desirable for Software-as-a-Service (SaaS). Read more