Contributed Content
My API Story: Conformance certified APIs
We talk to Vivek Verma, Technical Director, BSS Portfolio, Comviva, which provides digital VAS, mobile finance and customer management solutions to telecom operators and has achieved gold level TM Forum Open API Conformance Certification. He explains the benefits of TM Forum Open APIs, including how they save time in designing, developing and delivering applications to ensure customer satisfaction.
My API Story: Conformance certified APIs
Tell us about yourself and your job
As a part of BSS group in Comviva I drive the engineering and delivery function. My primary responsibilities are 3D's - designing, developing and delivering applications, role demand to keep pace with the latest technologies in the market and ensuring high customer satisfaction through bug free continuous software deliveries. Along with maintaining key parameters, one of the key areas we are largely focusing on is reducing time to market, that can be through adoption of the Open Digital Architecture, reducing deployment and integration time.
Why do you believe in TM Forum’s Open API program?
Comviva is focused on product innovation, digital business transformation and meeting the emerging expectations of the global communications industry.
We are committed to driving interoperability with an open digital ecosystem and the fact that we have achieved gold level TM Forum Open API Conformance Certification is a true testament of our efforts to drive the digital business transformation and innovation agenda for our clients.
The Open API program is strongly aligned to our business and technology strategy to accelerate the digital journey and drive business agility for our clients.
What TM Forum Open APIs are most valuable to your company?
Open API program is strongly aligned to our business and technology strategy hence all API’s are important to us, we are transforming and using API’s as per priorities, few we have already worked upon are TMF666: Account Management API, TMF629: Customer Management API, TMF640: Service Activation and Configuration API, TMF641: Service Ordering Management API, TMF621: Trouble Ticket API, TMF635: Usage Management API, TMF681: Communication API, TMF676: Payment Management API, TMF683: Party Interaction Management API, TMF678: Customer Bill Management API and TMF639: Resource Inventory Management API.
Why did you choose to highlight those APIs?
Integration standardization is the key principle we focus on while designing our system and these Open APIs are prioritized in line with the core functionalities to be released. With this same vision we have opted for a set of APIs and keep on enlarging our API inventory.
How do you use those APIs?
Key platform capabilities need to be leveraged through APIs for internal and external usage to maintain uniformity in business value delivered through platform or integration. We are developing and consuming APIs based on the same principle.
How have you benefited from using these APIs?
TM Forum Open APIs have contributed to defining our transformation strategy which has moved a long way from monolithic to microservices architecture. One of the key challenges in today’s world is complexity and designing an integration framework between various integrating platforms and TM Forum Open APIs provides the means to conquer this challenge. A lot of time is saved in R&D and API design as the Open API definition is already present.
Where do you use the APIs?
Our new BSS platform follows the TM Forum standards, and all internal and external exposed APIs are aligned to Open APIs. One of our ongoing deployments is following TM Forum Open APIs.
Read more stories from the "My API Story" library
