Number Verification
Confirm Phone Ownership Silently — No OTP, No User Interaction.
The CAMARA Number Verification API uses two complementary mechanisms: the operator's network identifies which subscriber a connected device belongs to (network-based), and the SIM installed in the device authenticates the subscriber (SIM-based). The result is cryptographic phone number confirmation delivered through a standard OAuth 2.0 Authorization Code flow — entirely transparent to the user.
How It Works
Three simple steps from API integration to real-time network intelligence.
Initiate the OAuth 2.0 Auth Flow
Your backend triggers an Authorization Code grant. The user's device connects through the mobile network — the operator intercepts the request to identify the subscriber.
Network Authenticates the SIM
The operator validates the SIM card currently in the device and issues an authorization code. No SMS is sent. No code is shown. The user sees nothing.
Verify or Retrieve the Number
Exchange the code for a token, then call /verify to check if a given number matches the device, or /device-phone-number to retrieve the number the network authenticated — two endpoints, two use cases.
The Network-Level Difference
Moving beyond application-layer security to direct mobile network validation.
SMS OTP Is Expensive, Slow, and Broken by SIM Swap
SMS one-time passwords carry a 20% abandonment rate as users switch apps, wait for delayed delivery, or simply give up. Worse, SMS OTP is the exact mechanism SIM swap attacks are designed to defeat — an attacker who controls your user's number receives every verification code you send, silently bypassing your entire authentication layer.
Network-Layer Identity — Two Endpoints, Two Powers
The /verify endpoint lets you check whether a phone number you already know matches the device currently on the network — ideal for onboarding confirmation and login. The /device-phone-number endpoint retrieves the network-authenticated number directly — ideal when you don't have the number yet and want the operator to supply it without any user input.
Industry Applications
Deployed across industries that demand network-grade trust and real-time reliability.
App Onboarding & Registration
Confirm the phone number a user typed during sign-up matches the SIM in their device — silently, during the same flow, with no OTP friction.
Passwordless & Silent Login
For returning users on mobile, authenticate them via network SIM verification — no password field, no code to enter, no app switching.
High-Value Transaction Step-Up
Re-verify identity at the moment of a sensitive action — payment authorization, address change, or beneficiary addition — without interrupting the user journey with an OTP.
Built on Open Standards
# Exchange code for 3-legged token (network-authenticated)
POST /oauth2/token
grant_type=authorization_code&code={auth_code}
# Endpoint 1: Verify a known number matches the device
POST /number-verification/v2/verify
Authorization: Bearer {access_token}
{ "phoneNumber": "+447911123456" }
// 200 OK
{ "devicePhoneNumberVerified": true }
# Endpoint 2: Retrieve the device's number directly
GET /number-verification/v2/device-phone-number
// → { "devicePhoneNumber": "+447911123456" }Start with Number Verification
Connect to the CAMARA network API in hours, not months. Our team handles operator relationships and compliance so you can focus on building.