Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

API Products: Who, What, Where, When, Why, and How?

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Cargando en…3
×

Eche un vistazo a continuación

1 de 17 Anuncio

API Products: Who, What, Where, When, Why, and How?

Descargar para leer sin conexión

A presentation given by Alan Glickenhouse, API Business Strategist, IBM, at our API-as-a-Product LiveCast on April 28, 2021. Watch the presentation here: https://youtu.be/mG2LChcXxA0

Learn more about the event: https://nordicapis.com/events/livecast-api-as-a-product/

A presentation given by Alan Glickenhouse, API Business Strategist, IBM, at our API-as-a-Product LiveCast on April 28, 2021. Watch the presentation here: https://youtu.be/mG2LChcXxA0

Learn more about the event: https://nordicapis.com/events/livecast-api-as-a-product/

Anuncio
Anuncio

Más Contenido Relacionado

Presentaciones para usted (20)

Similares a API Products: Who, What, Where, When, Why, and How? (20)

Anuncio

Más de Nordic APIs (20)

Más reciente (20)

Anuncio

API Products: Who, What, Where, When, Why, and How?

  1. 1. © 2021 IBM Corporation API Products –Who, What,Where,When, Why, and How? AlanGlickenhouse glick@us.ibm.com @ARGlick DigitalTransformation Business Strategist IBM
  2. 2. Profile: © 2021 IBM Corporation Alan Glickenhouse - Digital Transformation Business Strategist • Assist businesses with their strategy for Digital Transformation, Integration, and the API Economy - all industries, all geographies, and of all sizes. • Share insights and best practices through: • 1:1 workshops • Conferences / Events • Author: • Digital Business / Digital Transformation - 21 • API Economy / API Management Basics - 16 • Business and Value - 25 • Strategy, Governance, and Best Practices - 36 • Architecture, Technology, and IBM Products - 26 • Industry Standards and Use cases - 40 Today we will cover a few from these categories https://www.antwak.com/author/alan-glickenhouse-184 - job role mentoring videos
  3. 3. Agenda 3 API Products:
  4. 4. API Products:What? 4 An API Product is an API offering made available to a target market to satisfy a customer’s needs Acquisition options i.e., “plans” which are terms and conditions for use can enhance consumability. This may include: • usage limits (i.e., rate limits) • pricing options. API 1 API 2 API 3 API 4 Typically establish security around the API Product to ensure the appropriate access is granted only to the target community(s) and verify their identity and authorization as the API product is acquired and used.
  5. 5. API Products:Who? 5 API Product Manager Before 1. Identify the target market / consumer and their needs After 2. Drive the consumption of the API Product • Identify a desired target audience (internal or external) • Understand the needs of that audience. • Work with the API Developer role to build the necessary API(s) to satisfy the identified needs • Create the product offering package (i.e., API Product) and determine/establish the “plans” that will be offered. • Communicate the existence of the API Product to the target audience • Demonstrate the value of the API product to drive consumption • Measure the results and adjust marketing activities or product capabilities
  6. 6. API Products:When and How? 6 Use an API Management product (e.g., IBM API Connect) that supplies an API lifecycle process to: • create, • secure, • manage, • socialize, and • analyze the creation of APIs and API Products. At the appropriate stage in the lifecycle, the API Management solution assists the product manager in creating the API Product offering.
  7. 7. API Products:Where? 7 An API Portal Potential consumers are shown the set of API Products that the Product manager wishes to offer to them. The consumer explores the offerings and signs up to use the API Products. To help drive the acquisition, the product manager and API Developer often supply: • code samples, • documentation, and • the ability to try the included APIs before the consumer needs to sign up for the API offering.
  8. 8. API Products:Why? 8 Does NOT Work! • We are building APIs because we want someone to use them. Do NOT assume that all you need to do is make the APIs available. • API Products are all about driving the consumption of our APIs. • We are fighting for the attention of an audience. • Without API products, we would be supplying a set of parts and requiring the consumer to figure out what they need to solve their problem. • Putting this burden on the consumer may drive them to look elsewhere for an easier to consume solution. Okay, but Why do we want them to use our APIs?
  9. 9. ButWhy APIs? 9 APIs allow business assets to be securely and easily consumed and used by developers. API Business Driver Goal Result Speed Reach Innovation Share Deliver new offerings to market faster Obtain more customers Create new offerings / Fail fast Avoid duplication of work and data Revenue Revenue Revenue / Save money Save money The REAL API Monetization!
  10. 10.  Drives Adoptions of APIs  Typically low valued assets  Drive brand loyalty  Enter new channels For Free Facebook Login API provides free authentication for any Web / mobile app Example: Developer Pays  Business Asset must be of high value to the Developer  For example, marketing analytics, news,  Capabilities such as credit checks Example: Developer Gets Paid  Provides incentive for developer to leverage web API  Ad placements  Percentage of revenue sold product or services Google AdSense APIs pay developers who include advertising content into apps Example: Indirect  Use of API achieves some goal that drives business model.  E.g., Increase awareness of specific content, or offerings eBay Trading APIs offer developers access to trading services extending the reach of listings and transactions Example: The Business ofAPIs - Monetization API Monetization Understanding Business Model Options IBM Cloud – No cost trials, pay per use, scale up and down
  11. 11. API Monetization Options APIs Developer Pays Developer Gets Paid Free Indirect Pay as you go Freemium Tiered Points Based Transaction Fee Revenue Share Affiliate Referral Content Acquisition Content Syndication Internal - Consumer Internal – non-consumer B2B - Customer B2B - Partner Business Expansion
  12. 12. Key Questions 12 • Is the asset valuable or is exposing the asset a cost of doing business? • Who is it valuable to – the API Consumer or End User? • Do you own (or want to own) the customer relationship or does the API Consumer own the relationship? • Will pricing the asset cause the API consumer to be reluctant to use your services and will this decrease your access to customers? • Is the API Consumer working on your behalf (i.e., should you pay them)? • Is there a tiered structure that makes sense based on usage (e.g., lower utilization free to obtain market presence)?
  13. 13. Summary API Product API Product Manager API Portal API Management SW API Lifecycle $ Any Questions?
  14. 14. Additional Resources © 2021 IBM Corporation
  15. 15. Alan’s Articles, Blogs, Papers, andVideos… https://community.ibm.com/community/user/blogs/alan-glickenhouse1/2021 (change year for each year’s content) API Economy and API Management Basics: •. What is an API? and What is the API Economy? • What is API Management? • Alan Tells All About APIs (old video – no longer available) • IT Uncensored – What is API Management? (video) • What are businesses doing with APIs and why are they doing it? (video) • API Economy Drivers • Happy API Year! (from 2017) • I Already Have Partners Accessing My Services. Why Should I Use APIs? • Should Business APIs Replace EDI? • Providing APIs or Managing APIs – There is a Big Difference • Don’t be Afraid of Public APIs • Does size matter? (for your business to participate in the API Economy) • API Connect Video Series: API Economy – What’s happening and where is this going? (Part 1) and (Part 2) (video) •APIs and Events – Recognizing Opportunities Instead of Reacting to Problems •The Biggest Impediment to API Economy Growth is…? • Is Two-Speed (Bimodal) IT a Good Thing or a Bad Thing? Digital Business / Digital Transformation / Cloud Integration: • Becoming a Digital Business – Is API Management Enough? • Digital Transformation – Becoming a Digital Business • Digital Business and APIs – Need to See the Forest and the Trees (article) • Digital Business Value when Combining API Management and Istio • Digital Transformation Requires Integration Modernization • Integration Modernization Requires Good Parenting • Why Become a Digital Business? • How Systemized Innovation Enables Digital Transformation (article) • History of IT Constraints – What Might Constrain Digital Transformation? • Creating A Digital Ecosystem – Past, Present, and Future • Business APIs – The Secret Sauce in Successful Digital Marketing (article) • Overcoming the 3 Largest Obstacles to Digital Transformation (article) • Covid-19 and Cloud Integration 1 – Moving Forward • Covid-19 and Cloud Integration 2 - Immediate Actions • Covid-19 and Cloud Integration 3 - Shopping and Supply Chains • Covid-19 and Cloud Integration 4 – Supporting Your Customers • Covid-19 and Cloud Integration 5 – Government Scenarios • Covid-19 and Cloud Integration 6 - Service businesses, Recreation, Entertainment, Travel, and Risk management • Covid-19 and Cloud Integration 7 - Call to Action • Good Integration Patterns Never Die, You Just Add More • A Perspective on Current Integration Scenarios and What Might Follow
  16. 16. Alan’s Articles, Blogs, Papers, and Videos… Business and Value • Why Your Business Needs APIs (and Why Your APIs Need IBM API Connect) (white paper) + Blog • Why Choose IBM API Connect? • API Monetization – What Does It Really Mean? • API Connect Video Series: API Monetization (video) • API Monetization Understanding Business Model Options (white paper) + Blog • Gartner Once Again Recognized IBM as a Leader in 2020 Magic Quadrant (2020) •Gartner Once Again Recognized IBM API Connect as a Leader in 2019 Magic Quadrant (2019) • IBM’s API Management Undisputed #1 in Market Share – Again (2019) • IBM’s API Management Undisputed #1 in Market Share (2018) • Analyst Firm Lists IBM API Connect as an API Management Leader (2020) • Analyst Firm Lists IBM API Connect as an API Management Leader (2018) • Analysts Cite IBM as a Leader (2016) • What is the ROI for API Connect? – Forrester TEI Study Demonstrates Economic Benefits • Forrester TEI Study Results Show 674% ROI • RFP Template – Assistance in Choosing an API Solution Partner • IBM API Connect: Powering the New Channel • Do APIs Cause Channel Issues and Loss of Direct Customer Interaction? • State of the API Economy (video interview) • State of the API Economy 2020 • State of the API Economy – January 2019 • How to Get the Business to Participate in an API Initiative • How IBM API Connect Helps Royal Mail Group Deliver • The Business of API Marketplaces (article) • Now Trending: API Platform Economy (article) • Ecosystem and Marketplace Strategy with Alan Glickenhouse of IBM (interview) Strategy, Governance, and Best Practices • Creating an API Economy Strategy • Creating an API Economy Strategy – short version (video) • Implementing Governance of an API Initiative • Organization and Governance of API Initiatives • What are the Recommended Roles for an API Initiative? • What is the Recommended Organizational Structure for an API Initiative? • Real World Experiences with API Centers of Excellence (CoE) • Recommendations for an API Economy Center of Excellence (white paper) + Blog • API Center of Excellence and Governance (interview) • API Economy Best Practices (white paper) + Blog • API Connect Video Series: API Economy Best Practices (video) • Identifying Good Candidates for APIs • The 7 Biggest Mistakes Companies Make on their API Initiatives • GDPR Considerations for Integration and the API Economy • API Management Across Multiple Lines of Business (LoBs) • API Versioning – Best Practices (and not so great practices) • API Connect Video Series: API Use Cases (video) • API Economy – 4 Business Drivers and 7 Use Case Categories – Series Overview • API Economy Business Drivers: #1 – Speed • API Economy Business Drivers: #2 – Reach • API Economy Business Drivers: #3 – Innovation • API Economy Business Drivers: #4 – Domains • API Economy Use Case Identification: #1 – Mobile • API Economy Use Case Identification: #2 – Social • API Economy Use Case Identification: #3 – Data • API Economy Use Case Identification: #4 – Other • API Economy Use Case Identification: #5 – Partner • API Economy Use Case Identification: #6 – Public • API Economy Use Case Identification: #7 – IoT • API Products – Who, What, Where, When, Why, and How • Beating (or Catching Up with) the Competition through APIs • The API Economy Journey Map: How Are You Doing? • API Economy Journey Map FAQs • Discussing Your API Initiative With the Legal Department • Why Isn’t My API Achieving the Desired Results? • Changing Culture – How Committed Are You? (article)
  17. 17. Alan’s Articles, Blogs, Papers, and Videos… Industry • FAQ – Which Geographies and Industries are Most Advanced in the API Economy (article) • API use cases for every industry • APIs for Aerospace and Defense Blast Off • What’s driving APIs in Automotive? • Identifying API Use Cases: Automotive (white paper) + Blog • Banking on APIs • Banking on APIs – part 1 and part 2 (podcast) • PSD2: Banking and the API Economy (video panel discussion) • Q&A with the Head of Technology at Open Banking Ltd. • Identifying API Use Cases: Banking (white paper) + Blog • Drilling into API usage in Chemical and Petroleum • APIs for CPG – Managing Bathrooms to Supply Chains • Learning your ABCs using APIs – APIs in Education • No Shock the Electronics Industry is Charged Up about APIs • Financial Services – Planning to Retire on APIs • Identifying API Use Cases: Life Insurance / Financial (white paper) + Blog • Government APIs – Do More with Less • Identifying API Use Cases: Government (white paper) + Blog • Healthcare APIs – A Cure to Accessing Healthcare Systems • Healthcare Providers – A Prescription for APIs • Identifying API Use Cases: Healthcare / Life Sciences (white paper) + Blog • Healthcare and APIs (podcast) • Sample API Use Cases for Insurance (article) • Creating an Insurance API Platform (article) • APIs for Insurance – Avoid the Risk of Falling Behind • Identifying API Use Cases: P&C Insurance (white paper) + Blog • Legal vs IT: Usage of APIs throughout the Business (article) • APIs: A Prescription for Challenges in Life Sciences • Building APIs for the Manufacturing Industry • Media and Entertainment – Hooray for APIs! • Unearthing API Use Cases in Metals and Mining • Today’s Special: APIs for the Retail Industry • Identifying API Use Cases: Retail (white paper) + Blog • ReshAPIng Cities – Using APIs to Build Smarter Cities • Software Industry API Use Cases – Eating Our Own Cooking • Telecom and APIs – Now We Are Talking • Identifying API Use Cases: Telecommunications (white paper) + Blog • APIs are Taking Off In Travel and Transportation • APIs for Utilities – Let’s Do Something About the Weather! • API Industry Standards and Regulatory Requirements Architecture, Technology, and IBM Products • Introducing API Connect (video) • APIs and SOA – Better Together (video) • API Connect Video Series: APIs and Services What’s the difference? (video) • Positioning APIs and Services – Let’s End the Confusion! • How To Get To Two Speed IT • An ESB is Not API Management • Is a Combined ESB and API Management a Good Idea? • IBM Brings Multiple Integrations To a Single Platform; Focuses on Optimizing Integration for the Multi-Cloud Enterprise (interview) • Using APIs and Microservices as a Fast, Low-Cost and Low-Risk Innovation Engine (article) • API Connect Video Series: IOT – Focus on Security (video) • Internet of Things APIs – Focus on Security • Analytics: The Icing on Top of Your API Management Cake •Clearing Up Misconceptions About APIs and Microservices •Which Comes First, The API or The Service? •Do Not Be Afraid of API Initiative SUCCESS •Integration Architecture Decisions – APIs, Services, and Microservices •Use API-First Design to Address Multi-Cloud Architectures (article) •How Do You Ensure API Quality? • API Connect V2018 Whitepaper Now Available • Ping Identity and IBM Partner to Protect Against API Cyberattacks • IBM API Connect Wins 2019 iF Design Award • Integration Monitoring – Do You See the Trunk or the Entire Elephant? • Today’s Biggest IT Constraint – Break Through It! • Focus on the API Developer (article) • Principles for API Security (white paper) + Blog • Plan Ahead! Don’t Build an API Superhighway into a Cul-de-sac

Notas del editor

  • First, what is a product? According to Wikipedia, “In marketing, a product is an object or system made available for consumer use; it is anything that can be offered to a market to satisfy the desire or need of a customer.”

    Applying the definition of product to APIs, an API Product is an API offering made available for consumer use that is offered to a target market to satisfy a customer’s needs. While a simple statement, there is much behind this. First, notice the focus on “consumer/customer”. An API product should be an attractive offering to a customer. The implication of this is that we know what a customer wants (more on how we find that out to follow later).
     
    Assuming we have this information, we then need to build the API Product to meet this need. Is a single API the same as an API Product? The answer is that it could be. You might build a single API that meets the needs of a consumer and package it as a product to be offered to the market. Another possibility is that multiple APIs may be required to meet a customer need. In this case, rather than have the customer figure out what combination of APIs they need we can package multiple APIs as a single API Product and offer this package to the market as a simpler way to acquire the necessary solution. So, an API Product can contain one or more than one API.
     
    Further, to make the API Product attractive to the market we may want to enhance the offering with some acquisition options. API Products can contain “plans” which are terms and conditions for use. This may include usage limits (i.e. rate limits) where consumers can sign up for the usage they require. It could also include pricing options.
     
    Of course, we also need to establish the necessary security around the API Product to ensure the appropriate access is granted only to the target community(s) and verify their identity and authorization as the API product is acquired and used.
     
    Let’s make a comparison to purchasing a car. While there are some people who want to buy all the individual parts and build a car, most consumers want to buy a car as a complete working vehicle. Offering a complete car is far more consumable to most customers and they would be looking elsewhere if offered a collection of parts. Of course, the car does have models to choose from – EX, SX, LX, etc. and these are like the API Product concept of plans. Some people just need more than others! Finally, when we make our car purchase, we are given the keys. Not just anyone can use the car – Security!
  • Summarizing from these resources, the API Product Manager has two groups of activities related to API Products:
    Identifying the target market / consumer and their needs This can be broken down as follows:
    The product manager must identify an intended desired target audience for an offering and understand the needs of that audience. Note that this audience can be internal developers in the same company or external developers outside the company.
    Then the Product Manager must work with the API Developer role to have the developer build the necessary API(s) to solve the identified needs
    The API Product Manager then creates the product offering package (i.e. API Product) and determines/establishes the “plans” that will be offered for acquisition of the product.
    Driving the consumption of the API Product by the target consumer This includes the following:
    Executing a set of activities to communicate the existence of the API Product to the target audience and demonstrate the value of the offering to drive consumption of the API product
    Measure the results and adjust marketing activities or product capabilities of the API Product based on metrics or feedback from the consumers.
  • API Products are created as part of an API Lifecycle managed by an API Management product. At the appropriate stage in the lifecycle, the API Management solution assists the product manager in creating the API Product offering. For example, IBMs API Connect supplies a lifecycle management process to create, secure, manage, socialize, and analyze the creation of APIs and API Products. The lifecycle capabilities support many stages specifically focused on the creation and deployment of API products as part of the overall lifecycle
  • API Products are offered to consumers in an API Portal. API Portals are included in many full API Lifecycle Management solutions (such as IBM API Connect).
     
    When a potential consumer accesses the API Portal, they are shown the set of API Products that the Product manager wishes to offer to them. The consumer can explore the offerings and sign up to use the API Products that they would like to acquire. To assist the consumer and help drive the acquisition, the product manager and API Developer often supply code samples to invoke the included APIs, documentation, and the ability to try the included APIs before the consumer needs to sign up for the API offering.
  • If we are building APIs, there is only one reason we are doing this – because we want someone to use them. API Products are all about driving the consumption of our APIs. “If you build it, they will come” simply does not work! We are fighting for the attention of an audience and trying to drive their acquisition of an offering we have built. Without API products, we would be supplying a set of parts and requiring the consumer to figure out what they need to solve their problem. Putting this burden on the consumer may drive them to look elsewhere for an easier to consume solution. The simpler we can make the acquisition and the more complete we can make the offering, the more likely we are to succeed in our goal and drive the success of our API initiative

×