APIs are the new CLI.
I've said it repeatedly, and I'll say it again: APIs are the new CLI.
Increasingly, it is through an API that infrastructure and application services are provisioned, configured, and operated. Between automation and integration into deployment pipelines, the API is a critical component that every device - hardware, software, on-premises, or cloud - must have.
To produce a product without an API today is as unthinkable as delivering a device ten years ago without a CLI. To do business in the digital economy without an API is equally inconceivable.
To wit, MuleSoft in its "The Rising Value of APIs" research found that a mere 10% of organizations were deriving 0% of their revenue from APIs. The other 90% are generating varying percentages of revenue from their API efforts, with the bulk doing a brisk business via APIs.
Despite these impressive, revenue-generating results, it is actually productivity that is the most often experienced benefit of APIs. The aforementioned research notes that 58% of respondents claim improved productivity as a direct result of their API implementations.
Which is sort of amusing if you're a pedantic logician, because APIs on their own do not generate value or revenue. They do not improve productivity, nor do they enhance the user experience. Until an API is actually invoked - used - it has no value.
And that is why we're here today - to preach the importance of treating your APIs as part of the user experience.
According to the State of API Integration 2018, more than half (60%) of organizations drive API adoption by making them publicly available to any developer. Social media broadly falls into this category, as do many providers of products in just about every market. Indeed, F5 falls into that category with our iControlREST API that enables integrations, automation, and management of the BIG-IP platform. The API isn't all that useful if you don't have a BIG-IP, but if you do the API is public and supported by a robust community.
More than half (56%) also offer platforms that enable developers to build integration services. Just over a third (35%) offer SDKs to make integration easier for developers, and 42% are offering pre-built integrations that non-technical users can leverage.
The answer to 'who uses APIs' then seems to be easy: developers. But 'developers' is a broad term today that should encompass a variety of domains including software, operations, and even business. Because the truth is that a lot of folks (wave at the camera, NetOps) are using APIs to automate, orchestrate, and manage infrastructure, services, and applications today.
In other words, the users of your API are often the same as your users. And that means the API is necessarily part of the user experience.
One of the impacts of this is that APIs shouldn't - and really can't - be just a REST-enabled version of the CLI. In fact, based on responses in the State of API Integration, users are demanding APIs are tailored to meet the use case they're trying to build with them:
How Organizations are driving API adoption today
What is the highest demand from customers and partners for API integration?
The question today is no longer do you an API, it's do you have the right APIs. You may actually need to present more than one API. A public, granular API for focused integration, extension, or development of new products. Another "low-code" option for business users in addition to SDK-like offerings that focus on operations or workflows.
If you aren't treating your API as part of the user experience - and tailoring them to your target users - you may find adoption faltering and, by extension, your business.