What Have APIs Ever Done for Me: Three Years of GSMA Open Gateway

What has the GSMA’s Open Gateway programme achieved?

Looking back at the past three years of the GSMA’s Open Gateway programme, it’s hard not to feel proud and a little bit in awe of how much progress has been made in such a short time.

Today, over 300 network operators (302, to be exact) have access to Open Gateway network APIs. The GSMA’s market champion programme has worked closely with operators around the globe to support national launches of network APIs, often navigating the difficult challenge of uniting traditionally competing operators to collaborate positively within their markets. This has been particularly important for identity and verification APIs, which have had, and continue to have, such a positive impact in combatting fraud and scams.

The GSMA’s network API certification programme has been instrumental in helping operators and enterprises rapidly go to market, ensuring compliance and a common approach to implementing network APIs. This enables solutions to work effectively across nations and internationally, while also reducing implementation and testing costs.

This year, the API certification process has become automated, making it easier and faster to certify network APIs. The number of network APIs available has increased from the original four at the start of the programme, with over 70 APIs now available in the CAMARA repository and more than 24 available as “stable versions”. As the GSMA continues to collaborate closely with the CAMARA project on service APIs, the programme has also been joined by the TM Forum and Mplify (formerly the Metro Ethernet Forum), contributing “operate” and “LSO fixed-mobile convergence APIs” to the ecosystem.

Importantly, the Open Gateway Channel Partner ecosystem has grown exponentially, with a complex mix of aggregators, software companies, systems integrators and, most importantly, solution providers emerging to play an important role in monetising and driving adoption within the industry. Today, there are more than 80 active channel partners, including major global players such as Google, Meta, Red Hat, IBM and Oracle joining up.

During the course of the programme, we’ve seen the launch of the Ericsson joint venture, Aduna Global, with more than 15 mobile network operators within the consortium.

Finally, in England we have a saying: “the proof of the pudding is in the eating”, meaning the way you know something is good is when you actually use it. Probably the most important measure of the success of Open Gateway is the large number of mobile operators, that have launched commercial API-based services since 2023.

The role of the GSMA in driving technology adoption

When considering the Open Gateway programme, it is important to fully understand the role of the GSMA. As a member organisation, the role of the GSMA isn’t to bring new products and services to market; that is the role of the members themselves.

The role of the GSMA is to facilitate the adoption of new technologies, working with mobile operators, regulators, technology partners and other key stakeholders to address the technical, regulatory and compliance issues around new technologies. Nowhere has the GSMA been more successful than in its work promoting international roaming, and the GSMA has been uniquely placed to help drive adoption.

Open Gateway was what the GSMA called an “Unlock Future Potential” programme, where resources are allocated to support new technologies in “crossing the chasm” [1] between early innovators and early adopters, as technologies move from being an interesting concept to a commercially driven business solution capable of being implemented.

In effect, the role of the GSMA here has been to “prime the pumps” for a new technology and, once there is sufficient traction within the industry, to step back and allow market dynamics to take their course. We sometimes call this the point of “taking off the training wheels”.

Supercharging the network API economy

Application Programming Interfaces (APIs) are not new within the telecoms industry or the wider technology space. APIs are a method of standardising integrations to avoid expensive bespoke integrations, which can increase technical debt for MNOs.

Many mobile operators use their own proprietary APIs and have built significant businesses around them. These APIs reduce the cost of integration and technical debt, but they also create a fundamental problem for enterprises. They are proprietary to individual operators, which restricts their utility for enterprises that need to access their entire customer base, regardless of their choice of operator. Furthermore, this restricts the total addressable market both within countries and internationally.

No bank wants to introduce an API-based anti-fraud solution that only works with a single operator within that market, perhaps giving it, at best, 30–40% market penetration, just as no airline wants to introduce a seamless identity verification solution that is different for every single airport it flies to.

The GSMA programme has further enhanced that capability with market champions to drive adoption within key target markets, enabling collaboration, under the GSMA’s own strict anti-trust rules, as well as working closely with governments and regulators to help them understand the huge benefits of this approach especially when this collaboration may seem counter-intuitive.

The strength of Open Gateway, and why we believe it supercharges the network API economy, is that the Open Gateway concept is based on standardised APIs available across multiple markets and operators. So, if a bank introduces a series of anti-scam measures utilising Number Verification 2.0 and SIM Swap 1.5, that solution will work across the country for any operator that has implemented Number Verification 2.0 and SIM Swap 1.5 in its network, as well as for operators in other countries that have the same capability. This ability to roll out solutions nationally and internationally allows scalability and makes them more attractive to solution developers and enterprises, which can rely on standard builds for their solutions. The ability to roll out one solution to 100% of a national market, as well as across multiple markets, makes adoption that much easier.

The GSMA programme has further enhanced that capability with market champions to drive adoption within key target markets, enabling collaboration under the GSMA’s own strict anti-trust rules, as well as working closely with governments and regulators to help them understand the huge benefits of this approach, especially when this collaboration may seem counter-intuitive.

The role of the Linux Foundation CAMARA Project

While the GSMA is the champion and lead for Open Gateway, CAMARA plays a vital role in the creation and hosting of network APIs, providing the repository for around 70 network APIs. The GSMA further enhances the role of CAMARA by acting as the testing and certification programme for Open Gateway (Scam Signal), CAMARA (70+) and TM Forum (3) APIs. Certification ensures APIs are fully compliant with the API specification and that each API is implemented in the same manner. Testing and certification further reduce the effort required to implement an API-based solution and reduce future technical debt. This brings us much closer to the expectation of “out-of-the-box” implementations for solutions, while also reducing time-to-market and time-to-revenue, all of which drive market adoption.

The GSMA has worked closely with CAMARA throughout the programme and this unique power to collaborate is another important aspect of the programme.

API categories and adoption

There are many ways to break down and categorise network APIs to aid understanding, and possibly the most recent categorisation best helps us understand the state of the global network API market. Andrew Collinson, lead analyst at CPaaSAA, proposed three simple categories:

  1. Mobile Identity and Verification (Cash Cow)
  2. Location Services (Problem Child)
  3. Network Quality (Rising Star)

Mobile Identity and Verification APIs are among the most successful APIs deployed today, with Number Verification, SIM Swap, Device Location and Know Your Customer (KYC) Match arguably among the most successful. They are widely used by banks and retailers to verify that users are who they say they are, and there is a strong use case for network APIs to augment or replace existing verification services, improving accuracy, security and customer experience.

It’s important to note that every revenue-generating service needs identity and verification as its core baseline for providing more advanced network API services. You need to verify the user before you start providing them with high-value services.

Location Services are still problematic in some markets, and there is more work to be done with governments, regulators and operators. Location services are potentially sensitive for reasons of privacy, consent and security. The power of these services means that many enterprises see a very clear opportunity to personalise and tailor services to their end users, but because of the potential for misuse, the industry is understandably cautious at this stage. As an industry, we need to be able to provide safe, secure and consensual location services. If we get this right, there is huge potential to create new and sustainable revenues.

Network Quality APIs are highly attractive to Mobile Network Operators (MNOs). They truly allow them to leverage the power of their networks and investments to provide unique capabilities that cannot be replicated by non-telecoms network operators. While there are still some questions being raised about net neutrality, the power and potential to provide differentiated network quality services is undeniable. China Mobile, working with the ubiquitous payment platform Alipay, invokes Quality on Demand (QoD) for the final payment stage of a mobile payment transaction, helping to ensure the payment goes through and delivering clear improvements in first-time payment completion. The GSMA has worked closely with Estonian company Elmo Remote, which uses QoD to support its remotely driven cars and vehicles. For MNOs, this is seen as the strongest category for new services and revenue streams.

Creating the network API ecosystem for the future

Over the past three years, we have seen an exponential rise in the number of channel partners joining the GSMA’s Channel Partner programme. The ecosystem has also evolved, with major multinational cloud and technology companies, as well as global systems integrators, helping to significantly expand the network API ecosystem.

The success of the programme has led to its transition from the “supply side” of network APIs, focused on the rollout and availability of APIs globally, to the “demand side”, focused on the enablement, creation and monetisation of network API-based services in the future.

We only sing when we’re winning: are we seeing all of the API successes?

Within the GSMA, we have started to suspect something quite unique about the network API market: “reality exceeds hype”. While we are seeing amazing traction in the network API market, we suspect that beyond the announcements there are a lot of companies “doing, not talking”, rolling out new revenue-generating network API-based services without advertising the full extent of their utilisation.

Looking at the TM Forum’s recent Catalyst programme and awards, it was interesting to see how many AI-based services actually relied upon network APIs but didn’t talk about them. When you looked deeper into the tech stack, you could see that network APIs were foundational. But in the past six months, people have started talking less about the APIs themselves and focusing more on the services they enable.

Is this success? It feels like this phenomenon is a sign of success. The tech industry doesn’t have a word for when a technology becomes so successful that it starts to be overlooked. We call this the “wheel” analogy. The wheel is a masterpiece of problem-solving and engineering, and while wheels are ubiquitous and engineers design them for cars, aeroplanes and bicycles, no one talks about the wheels as a core part of the solution anymore. If you buy a Ferrari, other luxury car brands are available, people will talk about the power, the colour and the safety features, but they never talk about the wheels. It is a given that cars have wheels, and without wheels, is an automobile even a car? When you think about this comparison, remember that the Ancient Egyptians built the pyramids without access to new-fangled wheel technology.

It feels as if standardised network APIs are becoming the de facto approach to creating these network services. This feels like real success.

Something better change: our work is done, but there is still work to be done

It would be foolish to think that after three years everything that needs to be done to drive adoption of network APIs has been done. We are still at a relatively early stage with network API adoption and as we know it can take years for new technologies to take off.

There are still some major challenges to be addressed. Issues around regulation, consent and privacy. Work on pricing models and pricing. Work on improving implementation of network based services as well as encouraging more an more innovation in this space.

Finally, and perhaps most importantly there is still huge amount of work to be done to bring MNOs and Channel Partners together with enterprises, then end-users, because the true value of network API services is that while they have some consumer use cases the vast majority of use cases are B2B, B2G or B2B2C. Network APIs have the potential to unlock new enterprise revenue streams and make MNOs true partners to enterprises rather than simply a commoditised connectivity provider to enterprise. However, to get to that point there is a significant need for discovery, education and enablement with enterprise verticals.

Pivoting from supply to demand

It could be argued that the GSMA is reducing its support for network APIs too early, but network APIs are here to stay and have become a core part of the GSMA’s capabilities.

It’s not enough to build it; you have to lay on the tickets and arrange the transport to get people to come. This is what will help ensure network APIs become a commercial success.

What’s about to unfold: The Open Gateway campaign

Over the next 10 weeks, the GSMA will be sharing insights into the phenomenal success of the Open Gateway programme and how a simple discussion between a handful of mobile network operators has developed into a community of more than 300 operators, with around 86% API availability, 70+ network APIs and 80+ channel partners.

We’ve come a long way in the past three years, and we plan to show you just how far with our new campaign.