NashTech

Productisation of APIs to sell a combination of existing APIs

Productisation of APIs to sell a combination of existing APIs.

Industry
Technology
Introduction

With Apigee we can easily expose our APIs or subset of APIs to the client by creating a product. This product can then be monetised as per the company guidelines and expectations.

About Philips Healthcare

As we stepped towards the microservice architecture from the traditional monolithic architecture, we found ourselves hanging in between a lot of microservices, each one of them providing a set of unique feature/functionality. As a result, we had to deal with a lot many APIs. It was becoming a tough job to manage all these APIs on our own (approx 95+ APIs). That was the time when the management decided to move towards something which could provide us with the capability to manage and enhance the potential of our APIs, and that is when the integration with APIGEE-Servers took place, and a new era of development + management + scaling began.

To make the quality assessment processes more lean, efficient, effective, and standardised NashTech team was asked to conduct a Proof of Concept(POC) and provide a solution. The objective of this proof of concept was to detect, classify and count wheat grains using Computer Vision and Deep Learning algorithms integrated with an App and the ability to visualise and evaluate the outcome of the assessment in a user interface with pre-defined metrics. The target was to reduce the turnaround time from 3 days to around 3 seconds.

The challenge

With Apigee in place, we could scale and manage our APIs, but still, we weren’t very sure how can we benefit from these APIs. How can we make profits out of those since earlier it was the complete product we offered to a client, but now clients only want to pay for specific functionality that they were interested in and not for the whole bunch of functionalities we were providing?

The solution

Following are the scenarios that we have covered for the Products provided to our clients for consumption:
1) Client Authentication: Providing a product for consumption to a client needs to be secured; it should work only for the client it is created for, and this leads to the fact of authentication of the client. We achieved this by combining the Product with the Verify Api Key policy from Apigee policy set and providing the secret key to the respective client so that they can access the product only when they pass this secret key. Secret keys are automatically generated in Apigee for any product created, and those needs to be shared with the client for whom the product was created. As the business is growing, we are also looking out for better and non-vulnerable security options like the OAuth v2.0 security strength provided by Apigee out of the box.

2) Restricted Calls: Every product is created with a mindset that it has to be associated with a monetisation(discussed later) plan. A 15$ plan for an employee product gives 250 calls/ day to be successfully made to the proxies in employee productivity. If the client hits request number 251 for the product on the same day, we restrict them and respond with a message that the limit for the day has been reached. There are other plans as well.

3) Geographical and IP address-based restrictions: This has not yet been fully implemented but is a work in progress where we are restricting clients based on their geographical locations and IP addresses so that our services remain unavailable in a certain part of the world that may be due to any obvious reasons like Government terms and policies.

We set the following monetisation capabilities on the products :

  • Rate plans: We create a variety of rate plans for the different products as per a particular product’s demand in the market. We can now also club together different API proxies under one name and provide them to the end user and generate revenue from them.
  • Setting limits: We can now set limits and monitor the performance of the APIs, also we receive automatic notifications for when the limits are reached. This helps to improve the client experience as well.

The outcome 

With Apigee we can easily expose our APIs or subset of APIs to the client by creating a product. This product can then be monetised as per the company guidelines and expectations.

Read more case studies

From rising above adversity to riding the wave of digital transformation in the education sector

Explore how NashTech help Trinity College London ride the wave of digital transformation in the education sector

AWS
AWS
Migrating and modernising the virtual learning environment to AWS for an enhanced experience

The migrated and modernised Moodle infrastructure means that The Open University can now take advantage of cloud benefits.

AWS
AWS
A glimpse into a year-long RPA journey with a leading digital advertising service

A glimpse into a year-long RPA journey with a leading digital advertising services and solutions provider and how NashTech helped them.

Our partnerships

Scroll to Top
SAMPLE TITLE
sample short
sample heading lorem isump
FREE WHITEPAPER
Unlock the power of knowledge with our new whitepaper
“Elevating User Experience for Product Owners”
FREE WHITEPAPER
Unlock the power of knowledge with our new whitepaper
“Elevating User Experience for Product Owners”