Use the API business model canvas to explore one API opportunity. Pick the opportunity with the highest impact on the customer journey.
Use the canvas to quickly describe the purpose and assumptions around the API’s design.
This one-page overview summarizes your API thinking. You get a more detailed design using the canvases and checklists in the next phases.
A business model covers all aspects of running a business or a product line, from customer segments, to channels, to operational activities, resources, and costs.
APIs provide a way to improve, change or add to your current business models. APIs are important if your goal is to create an internal and/or external platform. APIs can also help cut costs by re-using and sharing resources or to create a network effect in your business model.
If you looked already at the API Business Model Canvas –template, you noticed that the areas are numbers. You should fill in all key information in the numbered order. Don’t be afraid to do a few iterations though.
Write a short sentence based on the fields D and E telling the "what and why" of your API. Copy the feature fields D and E from the AVP Canvas to the Value proposition (1) field in API Canvas.
You have now looked at the problem from at least one customer segments perspective. Fill in API Consumer segments (2): what was the segment you thought about when doing the AVP Canvas? Who else could also use this API? This is a good place to talk to the people in charge of business development and partner relationships. Don’t forget also marketing and vendor management people.
How do developers find the API? How to ensure API is usable for them, how to understand what it can be used for? How to test drive it? How is their subscription approved? Do they have to sign an agreement? How do they give feedback, see the roadmap, take part in the discussion?
The channels are the ways and places from which the developers find and can find, buy/request access to your API.
What is the API Business model of this API?
Revenue model is part of the business model. Revenue model, indirect or direct, only covers the way in which the company receives money or compensation from a product or service. What we need to consider is that APIs can play many roles in a company’s business model.
Look at the features in the Value proposition field. What do you need to build or create to achieve the features? Don’t forget platforms, testing environments, and other supporting elements. You might need to create also non-API things: agreement templates, marketing materials etc.
Look at the field F in the AVP Canvas. Are there any existing APIs or other services that you can use to create the new API –features? What existing platforms, backend integrations, document templates etc. will you use?
Think about partners in this case as internal and external people outside your team. Look at the Key activities, Key resources, and all the API Consumer related fields. With whom do you need to co-operate to make these API –features alive and usable for the intended API Consumers?
You can either estimate the real costs or set maximum cost based on profit from the revenues. Figuring out real costs can be difficult before the architecture is designed. Remember the fixed monthly costs for running the architecture components. Also budget for continuous small development and maintenance. Include platform costs, licenses, and 3rd party API costs. The variable costs will usually increase to significant amounts per month when your API has over 1 million users.
Great APIs need skilled people and a good method, which let's you create APIs as products - fast.
APIOps Cycles method is vendor & technology-neutral.
Read the free e-book "The 8 wastes of lean in API development". Learn quick tips on how to remove the wastes using the APIOps Cycles method.