• Learn how to use the method & how other's use your API

    In a cyclic and iterative development method, the learning phase varies depending on the maturity of the API product and the persons involved.

     

    In Prototyping phase, the API Consumers are different when the API is in production. Learning can be achieved by gathering feedback or by interviewing API consumers and studying the analytics reports. In building just enough phase you'll learn what works, really. And in scaling phase you learn to remove bottlenecks.

     

    If you are already a pro with the method, continue to improve and start the next cycle.

  • The Cycle

    Great APIs are born when skilled people work collaboratively using a great business model.

    Jump start implementing APIs by picking up any of the eight phases befitting you

    1

    Business model

    Use API Canvases. Find the right value proposition to your API. Define impact to business model.

    2

    Lean Architecture

    3

    Build API

    Build APIs: Prototype, build or scale depending on what architecture phase you are on.

    4

    Audit your API

    Audit your API: Use the checklists to verify your API meets style, API management and security needs.

    6

    Mind the Developer Experience: Support and build developer community

    7

    Measure business and technical KPIs to reach goals

    8

    Learn from the results and improve your API and the process. Or learn the method for first time.

  • API Management key concepts and roles

    API business models

    API based business models are the core and starting point of of this method, together with value proposition. Business models are important, so the true purpose and customer segments for the API are found early. This not only helps transform business to new data and platform business models, but it helps to focus the development and secure customer buy-in and budget.

    Value proposition

    The value proposition describes the value that the customer/user of a specific product or service feels they receive as the result of using the product or service. APIs are products and just like in all products, users will need a good reason (=value proposition) to decide to use it (=conversion).

     

    You will use the API Value proposition canvas to work out the possible contents of the value proposition. When writing the value proposition down to the API business model canvas, you need to make sure it answers these questions:

    • How API Product in question solves problems or improves the situation for the selected API consumers?

    • What specific benefits are there to use this particular API instead of other integration methods for the selected API consumers?

    And then when building the API business model, you should also consider
    • Why external partners or customers should use our API instead of competitors’? (think about this if you are offering the API to external parties)

    API Product manager (or product owner)

    Traditional product managers are commercially and analytically oriented persons who rely on tools like market research and user studies, work with sales, marketing, and other stakeholders to create a product that will sell. In Agile development, product owner has typically less commercial responsibilities but is still a customer/stakeholder advocate and prioritizes items in the backlog according to the value they bring to the customers.

     

    The technical nature of APIs as products requires API Product owners to translate the value proposition into technical capabilities and the technical capabilities into business terms.

     

    Customers of API Product owners are software and technology developers, but also business developers of customers and partners. API Product owner needs to understand the specific nature and needs of these user groups. They also need to translate these into capabilities that his own team of backend developers understand and can actually build.

     

    One major task of API Product Manager is to explain and mitigate the risks and values of opening their company’s data and value propositions to the world as a platform and also figure out how to build customer value from networks of other companies and their API using or offering products.

    API Product managers require great communication, business and technical skills.

    Application service manager

    CRM application serves as an (indirect or direct) backend for specific APIs. Any changes to the CRM or any service breaks may affect the APIs depending on it and the API consuming applications. Any needs to add or make changes to the dependent APIs may require changes in the application serving as a backend. If requirements come from other teams or external partners and customers, funding and priority have to be negotiated. Service manager needs to do release plans, change requests and service break down notifications minding the APIs and API consumers. Requirements depend on architecture and dependency of the API layer.

    Information architect

    Responsible for designing how requirements need to be split into independent APIs, endpoints and attributes and how to negotiate requirements between payload sizes, privacy and confidentiality requirements, local legal requirements and business processes. In charge of making sure the naming standards and values are valid also outside the company data architecture and naming conventions. Ideally creates guidelines for API publishing developers and conducts reviews.

    Developer segments

    Developers are our API consumers, but also your potential paying customers, sales channel, outsourcing partners or innovation partners. Each segment has its reasons why we are interested in them, and they are interested in us, as well as their own unique needs, behaviours and logic.

     

    Typical developer segments regarding APIs are

    • Business developers (selling or developing new business models, products and services that use our APIs)

    • Software developers (software applications using APIs)

    • Technology developers (devices using APIs)

     

    It may be useful to split the segments even more, to internal developers and external developers or according to the product or platform segment or their interface expectation or their knowledge and skills about our company, our products or using APIs in general.

    User groups

    Depending on what kind of API management solution or product you use, there may be different names for specific default user groups, and usually, all management products allow creating company-specific user groups. Typically, users related to APIs are divided into these high-level groups

    • Guest users or unauthenticated users, who can see available APIs but are not able to make API calls

    • API consuming developers

    • API publishing developers

    • API management platform administrators (users who can administrate network settings, API publishing user accounts, overall security settings, etc.).

     

    In big companies, these user groups need almost always to be separated into smaller user groups, as not all consumers are allowed to use all APIs (private or partner APIs) and not all teams of API providing developers can even see, know or administrate all APIs.

  • Ready, steady, go!

    Join the mailing list to stay updated on method changes, events and training. Then you are ready to start!

×
Privacy policy
SECTION 1 - WHAT DO WE DO WITH YOUR INFORMATION?
When you browse our website, we automatically receive your computer’s internet protocol (IP) address in order to provide us with information that helps us learn about your browser and operating system. 

With your permission, we may send you emails about our site, new services, events and other updates.
SECTION 2 - CONSENT
How do you get my consent? 
When you provide us with personal information to complete a transaction, verify your credit card, place an order, arrange for a delivery or return a purchase, we imply that you consent to our collecting it and using it for that specific reason only. 
If we ask for your personal information for a secondary reason, like marketing, we will either ask you directly for your expressed consent, or provide you with an opportunity to say no.
How do I withdraw my consent? 
If after you opt-in, you change your mind, you may withdraw your consent for us to contact you, for the continued collection, use or disclosure of your information, at anytime, by contacting us at [email protected]
SECTION 3 - DISCLOSURE
We may disclose your personal information if we are required by law to do so or if you violate our Terms of Service.
SECTION 4 – SERVICE PROVIDERS
Our website is hosted on Strikingly Inc., a Delaware, US based company. They provide us with the website platform including the subscription and web form data you submit to us.
Your data is stored through Strikingly’s data storage, databases and the general Strikingly application. They store your data on a secure server behind a firewall. More information can be optained from their Privacy policy https://support.strikingly.com/hc/en-us/articles/214364818 
We use Google’s application suite for email, documents and calendar and Campaign monitor for sending email campaigns. We only allow dedicated personnel to get access to these systems. Emails sent to our general email [email protected] are also stored in PlanMill, our ERP system, for customer service and archiving.
SECTION 5 - THIRD-PARTY SERVICES
In general, the third-party providers used by us will only collect, use and disclose your information to the extent necessary to allow them to perform the services they provide to us. 
However, certain third-party service providers, such as payment gateways and other payment transaction processors, have their own privacy policies in respect to the information we are required to provide to them for your purchase-related transactions. 
For these providers, we recommend that you read their privacy policies so you can understand the manner in which your personal information will be handled by these providers. 
In particular, remember that certain providers may be located in or have facilities that are located a different jurisdiction than either you or us. So if you elect to proceed with a transaction that involves the services of a third-party service provider, then your information may become subject to the laws of the jurisdiction(s) in which that service provider or its facilities are located. 

Links 

When you click on links on our store, they may direct you away from our site. We are not responsible for the privacy practices of other sites and encourage you to read their privacy statements.
SECTION 6 - SECURITY
To protect your personal information, we take reasonable precautions and follow industry best practices to make sure it is not inappropriately lost, misused, accessed, disclosed, altered or destroyed. 

SECTION 7 - COOKIES
You are asked separately for accepting cookies on the site.
SECTION 8 - AGE OF CONSENT
By using this site, you represent that you are at least the age of majority in your state or province of residence, or that you are the age of majority in your state or province of residence and you have given us your consent to allow any of your minor dependents to use this site.
SECTION 9 - CHANGES TO THIS PRIVACY POLICY
We reserve the right to modify this privacy policy at any time, so please review it frequently. Changes and clarifications will take effect immediately upon their posting on the website. If we make material changes to this policy, we will notify you here that it has been updated, so that you are aware of what information we collect, how we use it, and under what circumstances, if any, we use and/or disclose it. 
If our store is acquired or merged with another company, your information may be transferred to the new owners so that we may continue to sell products to you.
QUESTIONS AND CONTACT INFORMATION
If you would like to: access, correct, amend or delete any personal information we have about you, register a complaint, or simply want more information contact our Privacy Compliance Officer at [email protected]
-----