Structure • Telecom Italia: Quantifying the Volume of API Transactions • Telecom Portugal: API Maturity Model • Telefonica: Partner for Cloud Services • Bouygues: Using the service broker to make telephony service innovation affordable • Mobily: API innovation • Tunisiana: Practical Business Analytics • Telefonica: Making payment services work • Vodafone: Delivering services or APIs – its both
The Telecom Italia presentation provided and excellent summary of API success with great quantified examples, overall the total transactions per month is close to 1B
The drive for TI’s API program came from the need to work more effectively with partners, the project started in 2008.
The APIs cover a broad set of capabilities, many of which are not covered in the standards. APIs include many IT related capabilities in provisioning customers.
This clearly demonstrates to focus on internal and partner applications of service exposure NOT the long tail, though they do not exclude the long tail.
This and the following 3 slides provide quantified examples of the volume of traffic goingover their API platform. Most of these transactions are associated with revenue earning events, not simply service usage (as in the case of cloud API transactions).
Clear demonstration on the maturity of APIs as processes are put in place to manage the API creation process.
Many of the next steps are focused on process improvement, not just additional APIs.
Great example of how an operator can build the platform themselves using off the shelf IT components, and frank review of where to focus with APIs
SDP supports existing business (meo, tmn and sapo), partners, and long tail developers. Heterogeneous development environment.
Example of how the News Stand API can be used across all PT platforms.
Comparing to the Web, the number of APIs is a tiny fraction of what it will become. We areonly at the start of the beginning of the impact APIs will have to all businesses. N.B. an API can be thought of as a machine readable webpage.