Number verification API
Network as Code provides identity and security capabilities that allow your applications to prevent
or proactively react to fraud by using resources that go beyond traditional 2FA authentication processes.
Instantly verify if a mobile phone number that a user provides is the same one being used on their device or not.
Service Providers can also confirm the mobile device's phone number (MSISDN),
which can be returned to them by this API.
These features provide an extra layer of security against fraud, such as SIM cloning or spoofing.
You can easily integrate the Number Verification functionalities to your applications and shield them with an extra layer of security against fraudulent attempts, such as SIM swapping.
What does this API do?
-
Verifies if the phone number provided is the same one being used by the mobile device.
-
Returns the device phone number that is linked to the authenticated end-user's access token
The Number Verification API supports two authentication paths:
- Number Verification V1 — network-based authentication using CAMARA's 3-legged OAuth 2.0 flow. The device must use a mobile data connection (not Wi-Fi, hotspot, or VPN).
- Number Verification V2 — SIM-based authentication using a TS.43 operator token obtained through OpenID4VP and the Android Credential Manager. Works over Wi-Fi and other connections.
Choosing between Number Verification V1 and V2
Both versions verify the same phone number claim. The choice between them mainly comes down to the device's connection and platform at the time of verification.
| Number Verification V1 | Number Verification V2 | |
|---|---|---|
| Connection | Requires a mobile data connection. Does not work over Wi-Fi, hotspot, or VPN. | Works over Wi-Fi and other connections, since it relies on a SIM-issued operator token instead of a network-based session. |
| Platform | Any browser or app that can open the CAMARA authorization URL. | Android only, and requires up-to-date Google Play Services for the Credential Manager. |
| Dependency | Does not depend on a TS.43 operator token, so it applies wherever operator token support is unavailable or not applicable. | Depends on obtaining a TS.43 operator token through OpenID4VP and the Android Credential Manager. |
| Retrieve device phone number | Supported — see Return the device phone number. | Not currently supported; use Number Verification V1 for this use case. |
Use Number Verification V1 when the device is on cellular data, when you need to retrieve the device phone number rather than verify a user-supplied one, or when the TS.43 operator token flow is not applicable (for example, non-Android platforms).
Use Number Verification V2 when the device may be off the home network (for example, on Wi-Fi) and you only need to verify a phone number on an Android device with Google Play Services.
Many integrations support both: attempt Number Verification V2 first for the best user experience, and fall back to Number Verification V1 when the device cannot produce an operator token (non-Android, outdated Play Services, or the user declines the OS dialog).
Terminology and acronyms
MSISDN: The phone number associated with a SIM card that you want to check.
What's behind this technology?
The Number verification functionality follows CAMARA definitions, which is an open-source project within Linux foundation. Network as Code bridges the gap between your application and the Operator platform making the connection seamless so you can retrieve phone number data. After you register on Network as Code Developer Portal and get consent and authorization for devices, you will be able to easily use and integrate this API into your applications.
Last updated September 18, 2026