A Number Verification API lets an app or website ask a user's mobile operator whether the phone number the user entered belongs to the SIM in the device they are using right now. The operator answers from its own network data, so no code is sent and the user types nothing. The open standard is the CAMARA NumberVerification API, part of the telecom industry's network-API programme known as GSMA Open Gateway.
How does the Number Verification API work?
The CAMARA project, hosted by the Linux Foundation, publishes the specification. It enables consumers to "verify the phone number associated with the SIM used in the device connected to the mobile data network" (CAMARA NumberVerification). Its latest public release is r4.2, published on 19 October 2026 with API version 2.1.1, a patch update of 2.1.0 (release notes).
The flow, simplified:
- The user enters their number in your app.
- The app starts an operator authorization flow over the mobile data connection, so the operator can see which SIM is making the request.
- Your backend calls the API with the number, in plain text or as a SHA-256 hash.
- The
verifyoperation returnsdevicePhoneNumberVerified: trueorfalse. A second operation,device-phone-number, returns the number the operator associates with the SIM, where the operator and the law allow it.
Operators expose the API directly or through aggregators, under the GSMA Open Gateway umbrella of "common network APIs". CAMARA also standardizes related APIs, such as SimSwap, which reports recent SIM changes on a number.
Which operators offer the Number Verification API in 2026?
There is no single public list of live deployments, so check per operator and per country. Two kinds of announcements get mixed up:
- Signed up to Open Gateway. According to the GSMA, as reported in March 2026, over 300 mobile networks covering around 80 percent of global mobile connections have signed up to Open Gateway (iTnews, 5 March 2026). Signing up is a commitment, not a live API.
- Live Number Verification. Telstra became the first Australian operator live with Open Gateway in March 2026, starting with the Number Verification API (same source). In Colombia, Claro, Movistar and Tigo presented SIM Swap and Number Verification as their first two Open Gateway APIs on 3 February 2026 (GSMA).
In practice, developers reach several operators through an aggregator rather than one contract per network, and coverage still varies inside a country: one operator may be live while another isn't. Plan for the API to answer for only part of your users.
Where does it stop working?
- Wi-Fi. The standard flow needs a mobile data connection. Other connections work only with extra SIM-based token mechanisms.
- Operator coverage. Availability is per operator and per country, and many users' operators don't offer it yet.
- Desktop. A laptop has no SIM, so desktop sign-ups need another method or a hand-off to the phone.
- Dual SIM and eSIM. If the data SIM isn't the SIM for the entered number, an honest user gets
false.
See silent authentication and flash call for the full list and the alternatives.
Why does it matter for fraud and deliverability?
Number verification proves possession without an OTP, so it removes three problems at once: no SMS fee, no SMS pumping target, and no code to phish. It can't tell you everything, though:
- It proves the device holds the number now. A recent SIM swap looks like a legitimate match.
- It doesn't tell you the line type or whether the number is a good contact channel.
- The fallback path, usually an SMS code, is where cost and fraud concentrate once the silent path is in place.
How does MobileValidate fit in?
MobileValidate doesn't offer operator number verification. Our checks run before it: a carrier lookup tells you the country, current network and line type, which decides whether a silent check is worth trying and how to protect the fallback. The OTP and sign-up fraud use case shows where each check fits. Unknown answers are free.
Frequently asked questions
What is the CAMARA Number Verification API?
It is an open API specification, maintained by the CAMARA project under the Linux Foundation and used in the GSMA Open Gateway programme. It lets an app ask the user's mobile operator whether the number the user entered is the number of the SIM in the device making the request.
Does the Number Verification API send an SMS?
No. The operator identifies the SIM from the device's mobile data connection, so nothing is sent and the user types no code. That is why it is often called silent authentication.
Which operators offer CAMARA Number Verification in 2026?
Availability is announced operator by operator. Examples from 2026: Telstra went live with it in Australia in March, and Claro, Movistar and Tigo presented it in Colombia in February. Signing up to GSMA Open Gateway, which more than 300 networks have done, is not the same as having the API live.
Does it work everywhere?
No. It depends on the user's operator offering the API, on the device being connected over mobile data, and on the SIM that carries data being the one for the number entered. Every flow needs a fallback.

