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
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
APIs are pretty important. You already know that, or you wouldn’t be a reader of this blog. To that end, we realize there’s an element of preaching to the converted in this post.
However, even some of those who understand the value of APIs may not know that there are countless companies out there that wouldn’t be around today without APIs. Read more
However one feels about sites like Freelancer, Upwork and People Per Hour, it’s difficult to deny that two-sided marketplaces have changed the face of on-demand work. Previously, freelancers have had to work (sometimes very hard) to ensure a constant flow of projects, and employers wasted resources finding expert talent. Read more
When creating an API, it’s all too easy to release something that “just works.” For some developers who aren’t working at an API-first company where the API is a central component to their business, they may see creating an API as a distraction from their core duties and rush to get a product out that does the job it’s supposed to, but little more than that. Read more