Mobile Connect is the GSMA's operator-backed identity and authentication standard, built on OpenID Connect, that lets a user authenticate to a service using their mobile subscription rather than a password. Together with the earlier OneAPI initiative it forms the prehistory of today's network APIs — the attempts that came before CAMARA and shaped what CAMARA deliberately did differently.
Mobile Connect
Understanding Mobile Connect and OneAPI is the fastest way to understand why CAMARA is built the way it is.
- OneAPI (2008 onwards) - The GSMA’s first serious attempt at a common operator API surface. The GSMA’s own Head of Future Networks has publicly called it a spectacular failure.
- Mobile Connect (2014 onwards) - Operator-federated identity on OpenID Connect, achieving what he characterises as moderate success — real deployments, never ubiquity.
- The lesson the industry drew - Specifications written as documentation did not survive contact with developers; specifications written as code, in public repositories, might.
- Still in the lineage - Some operators’ current KYC Match offerings trace to Mobile Connect rather than to CAMARA, which matters when assessing whether a claimed CAMARA implementation is really one.
The industry’s phrase for this history is this is not our first rodeo, and it is worth taking seriously as evidence rather than as self-deprecation. A standard is a second or third attempt more often than it is a first one, and the failures are where the design constraints come from.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of Telecom APIs
The GSMA's own Head of Future Networks calls OneAPI a spectacular failure and Mobile Connect a moderate success — the history that shaped why CAMARA is written as code, in public.
