API Digest #69: An API Recipe for the Disruption of Traditional Industries

7 July 2017 |

We are back with our traditional fortnight API Digest! So, ladies and gentlemen, let me introduce the next topics which you are going to read:

  • The return of the CLI: CLIs being used by API-related companies;
  • A view of the API lifecycle from James Higginbotham;
  • Great APIs are like Lego bricks;
  • API product ownership is key for API adoption;
  • How to value your data when providing an API;
  • How APIs are the backbone of new IoT standards;
  • An API recipe for the disruption of traditional industries;
  • Why SaaS and On-Prem software providers should think API-first.

Companies like Zapier, Curity, Amazon, and more are releasing CLIs alongside their API offerings to maximize their platform usage and better cater to the wants of their developers. In the article “The return of the CLI: CLIs being used by API-related companies”, Bill Doerrfeld explores CLIs reappearance within the SaaS platform stack.

There are a lot of companies who know they want APIs but don't have any real plan for getting there, beyond just putting a developer on it. Here is an API Lifecycle list from highly skilled enterprise API architect James Higginbotham. He focuses on the solutions brought to the table, as well as thinking about the realities of actually getting the work done.

Great APIs are like Lego bricks: easy to use, and people want to play with them. Art Anthony encourages to keep it in mind if you’re building a new API or reiterating an existing API. In most businesses, an API is likely to be seen as a secondary offering. It’s this view that Matthias Biehl, API consultant at API University, believes is totally outdated. An approach that puts APIs first can be a key business driver, with enormous financial potential, but only if it’s built to satisfy the needs of the developers who will be using it.

James Higginbotham believes that product ownership is essential to increased API adoption, as it moves teams beyond thinking about technology to solving problems for developers and business leaders. Great APIs help developers do extraordinary and necessary things, often with limited effort. They solve problems that matter to both business leaders and developers.

In the article“How to value your data when providing an API”, Chris Wood shows the motivation for exposing data via an API and the different types of data providers can expose. Also, you will find the specific value of this data from both the perspective of API providers who expose the data, and the consumers who use this data when building their applications.

Jennifer Riggins believes that APIs are the backbone of new IoT standards. The Web of Things working group, a part of the World Wide Web Consortium or W3C, has brought together 40 of the biggest players in the Internet of Things (IoT) space to standardize on semantic interoperability based on Linked Data and APIs.

The use of APIs is a good indicator of an enterprise’s ability to adapt to the digital needs of customers. APIs are at the heart of a business’ ability to develop products faster, seamlessly integrate data systems, and extend their reach to new partners and other value co-creators. If you’re wondering how traditional industries can become digital players by using APIs, Mark Boyd has an API recipe for the disruption of traditional industries.

Software is great — you write it once, and it just keeps on working forever with no changes. Except, of course, this is not true. :) It's always evolving, getting new features, and serving new audience. Dave Gray shows a few key API strategies and explains why SaaS and on-prem software providers should think API-first.

For more API news and insights, read API developer weekly #161 and #162 by Keith Casey and James Higginbotham.

See you in a fortnight! In the meanwhile, send us article suggestions and ideas. Either way, we are happy to hear from you. :)

P.S. In case you’d be interested in trying API2Cart, you can create an account and see how the API works on live stores.