A North American-Based Telecom Carrier Uses APIContext To Monitor their Third-Party APIs
Telecom carriers need to understand their third-party API suppliers
A major United States-based carrier with more than 100 million subscribers struggled to understand their third-party APIs. These APIs are used by enterprises and developers seeking to integrate with key backend carrier services.
They leveraged APIContext to monitor their APIs to open an API gateway for backend services including messaging, advertising, billing, location, and webRTC.
What You'll learn In this case study
The challenge was that developers and paying clients reported outages that were not being picked up by internal monitoring tools like AppDynamics or the Apigee API gateway.
Developers and clients felt a clear disconnect between their experience and the carrier’s own DevOps monitoring.
This brought up key questions:
▶ Were premium services delivering a premium experience? How could the carrier demonstrate that enhanced services were delivering on their obligations?
▶ Could the carrier show positive direct competitive comparisons between their APIs and commercial equivalents like Twilio?
▶ Was it possible to maintain or even improve API performance when services were updated?
Download Now
