Business models are constantly changing and APIs (Application Programming Interfaces) are a part of that change. "How so?" you may ask. To answer this, it's essential to first understand what an API actually is and how it relates to apps and the platform economy. API 101 answers these questions and helps you see how your company can also leverage the API Economy. Written by four API Economy professionals, the API 101 book will make you look at your business model from a new perspective. Below, we have listed seven realizations you can expect to have after reading the book. Don't say we didn't warn you!
When creating an API, the most important question is to what added value and to whom should the API produce.
In the shoes of the customer, the value includes a wide variety of benefits and sacrifices. Customers’ perceptions of value are personal and formed as a sum of various things. An API can be a product itself or an enabling factor as part of the customer’s value creation.
"The API is an interface for capturing the value proposition, not just an interface for the application"
When planning or building an API, it is important to make sure providers’ and customers’ needs (and expectations about the needs) meet. A common mistake is that the provider builds value that customers don't actually want or that they exclude some features that would have been needed.
“An ecosystem is made up of a multilayered group of partners, all of whom and their interactions are needed to materialize a key ecosystem value proposition.”
This is Ron Adnerd's (2017) definition of business ecosystems. The API economy ecosystem differs from the traditional platform ecosystem in terms of governance. In an API economy ecosystem, new services are constantly being created by different companies and as mashups of APIs and the focus is on APIs instead of the platform. This enables a new kind of value creation with external partners, competitors, and various network communities and customers.
In API Economy 101 book, one of the authors Marjukka Niinioja, answers the question on everyone’s lips: what is an API and what is its optimal role as part of a company’s business model and IT architecture.
API in itself can be a product, a service, a technology, or a resource. In a broader view, a change is moving from product orientated logic to service-dominant logic. When a company moves into API era, it must make an inventory of its resources in an API perspective.
But what resources really are? Marko Seppänen and Marjukka Niinioja developed a new model that describes the resources available to the company specifically in the API economy. More about the model on the book.
“The most important resources of the platform economy company are knowledge and APIs related to the resources of other companies and organizations.”
There is a reason why the teaching of business models is mainly done by canvas. Canvases force people to think their customers as a part of their business model. This customer-focused point of view is essential to the success of the API economy, not designing solutions based on the API provider, as well as focusing on the relationship between the provider and the market. Good tools for this are the API value proposition and API business model canvases.
“In the API economy, developer experience is a key part of
customer experience and business model success.”
After defining the role of APIs to your company, the next step is to figure out what kind of API serves you best. Questions to help API definition can be is API available anyone to register, is paid support available to adopting API or is there an open license for data?
The book goes reviews the features of different APIs, strategies to use it and impacts and benefits for your business.
As a target segment, API consumers are different from end- customers, who use the outputs of the API consumers. API consumers, that is, application developers, require their own direct and sales-jargon-free practices to deal with an API offering.
To overcome the chasm, the API developer and customer experience must be optimal. That’s why we focus on developer relationships.