To view recording of this webinar please use below URL: http://wso2.com/library/webinars/2016/03/how-to-enable-monetization-of-your-api-ecosystem/ In the modern world of digitization, APIs are opening up ventures for new business opportunities. Organizations have started realizing the value of their data and services and are pushing to sell them. In this era, it is important to find the right business model to generate maximum revenue through your APIs. You can leverage the WSO2 API Management platform to build your API monetization strategy. This session will look into WSO2 API Manager features and integration points to understand the roadmap to monetize your organization’s APIs. It will also discuss the following topics: The API billing model: Usage plans Integrating the API platform with a billing engine Monitoring your API usage Access control and rate limiting

2. WSO2 API Manager - Introduction
● Open Source API Management Platform
○ API Publishing
○ API Store (Developer Portal)
○ Subscription Management
○ Token Management
○ Throttling
○ Analytics
○ Scalable Deployment
● Part of the award winning WSO2 Carbon Platform
● Apache 2.0. Licensed
● Utilizes proven WSO2 Technology
○ WSO2 ESB
○ WSO2 Identity Server
○ WSO2 Governance Registry

3. Monetizing APIs - The Billing Model
● API Publishers bill API Consumers (App Developers) for API Consumption
● Each API is exposed over one or more Tiers
● API Consumer selects a tier of preference when subscribing to APIs
● API Consumer is invoiced based on the tiers consumed by his/her
Applications

4. Defining Usage Plans

5. Charging for over consumption

6. Discovering free APIs vs Billable APIs on the
Store

7. Registering users on the Billing System : The
API Subscription Workflow

8. Completing the Subscription Workflow

9. The API Subscription Workflow

10. API Subscription Workflow - Sequence Diagram

11. Invoicing: Monitoring Usage

12. Invoicing: Aggregate Data through the DAS
REST API.

13. Invoicing: Aggregate Data through RDBMS

14. Pros and Cons
Pros Cons
REST ● For Quick setup
● No need additional data source
● Suitable for less no of users and APIs
● Reduced deployment/configuration
complexities
● Less complex queries with
lucene queries
● Low performance for large data
● No database dependent
RDBMS ● Suitable for large users and APIs
● High performance for large data
● Support several RDBMS servers
(mysql, oracle, etc)
● Possible more complex queries
● Need Additional RDBMS
● Need Extra set-up time
● Database dependent

15. Retrieving Statistics from data source
● Statistics can be retrieved from either DAS REST API or RDBMS
● All the Statistics related events can be found on DAS
● Can use in built summary data provided with APIM
● Can be generate Custom summary Statistics if need
● Spark support large scale data processing

16. What happens when you don’t get paid?
● Use the block subscription REST API to bar API consumption from the
Application.
● Use the unblock subscription REST API to re-allow API consumption from the
Application

17. Protecting your back-end systems from over
exposure

18. Protecting your back-end systems from over
exposure

19. Protecting your back-end systems from over
exposure

20. Protecting your back-end systems from over
exposure
● Use API hard-throttling to protect your back-end systems.

21. Demo!

22. Thank You!!