My API story: accelerating integrations with a common language
As a Solution Architect for Thinkskink (TS), I focus on BSS where we orchestrate complex business processes with fast performance, failure tolerance, strong consistency, clean code and good design patterns.
For 15 years I have been closely working with business requirements around 2G, 3G & LTE technologies, and for the last 5 years I have been in touch with TM Forum in order to integrate existing APIs and design new features with Open APIs.
At TS we create products that can be easily consumed as a service by other systems. As part of the digital transformation movement, many vendors are using Open APIs to accelerate integrations with a common language.
TMF622 Product Ordering Management.
TS solutions focus on integration with multiple vendor’s billing, charging, and provisioning systems. It's often complex to define new service/API contracts when all the areas need to be in agreement, but it is easy to adopt the APIs that already exist and achieve the integration in a short time.
Due to the success of Open APIs in our product with our customers, we are implementing more and more Open APIs in our orchestrator product (TS-ROS).
TS products both exposes and consumes Open APIs.
We implemented a specific API in one of our clients to create product orders from eCommerce platforms and orchestrate product activations around legacy systems and network elements.
With another client we orchestrate multiple complex business processes consuming Open APIs from different vendors in order to add services and offers to existing and new clients.
Our customers are increasingly demanding that their integrations be through Open APIs. Open APIs truly minimize time to market and standardize integrations between multiple systems.
We use Open APIs in our customers in Latin America; in Mexico, Perú and Chile.