Everything worth knowing, nothing that isn't.
What APIs are in scope
The CAMARA project (a Linux Foundation initiative co-owned with GSMA) hosts the API definitions. Most-deployed: Number Verification (silent verification, replacing SMS OTP), SIM Swap (detect if a SIM has been swapped recently — anti-fraud), Device Status / Roaming, Quality on Demand (request guaranteed bandwidth for a session), and Location Verification. Less mature but in the spec: Carrier Billing, Edge Discovery, Network Slicing access.
Why it matters
Two reasons. First, anti-fraud — SIM Swap and Number Verification are step-changes in account-takeover prevention. A bank that calls the SIM Swap API before approving a high-value transaction catches SIM-swap fraud at the moment of attack, not after. Second, channel cost — silent Number Verification through Open Gateway is cheaper than SMS OTP at scale and has near-zero user friction.
Adoption state
As of 2026, 60+ operators across 40+ countries have launched at least one CAMARA API. MENA-active operators include STC, e&, du, Orange Egypt, Vodafone Egypt, and Zain. Coverage is uneven — Number Verification has the widest deployment; SIM Swap is rolling out through 2026. BroadNet aggregates Open Gateway APIs across MENA operators behind a single endpoint so you don't have to integrate per-operator.
What's still missing
Pricing transparency (operators set rates per-API per-region with little visibility). Cross-country roaming for the APIs (a Number Verification API call against a UK number when the subscriber is roaming in UAE is not yet reliably supported across all operator pairs). Latency consistency. Expect significant maturation through 2026-2027.