Emver
Emver
Profiden+ Blog
Contact & Address

Mobile Number Verification API

Validate a mobile number before you trust it: active status, operator and circle, prepaid or postpaid, and a name match against the subscriber record where available. Reduce fake sign-ups, unreachable candidates and misrouted OTPs.

Response
Real-time
Inputs
1 required · 1 optional
Consent
Recorded per request
Billing
Per successful call
POST /v1/mobile-number-verification
Sandbox · Production
  1. Your application sends

    • Mobile number*
    • Name to match
  2. Profiden API

    Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.

  3. Verified with

    Telecom operator data

  4. You receive

    • Active status
    • Operator and telecom circle
    • Connection type
    • Name match result where available
    • Ported (yes/no)
mobile-number-verification Full reference

What the Mobile Number Verification API does

A mobile number is the identifier every onboarding flow captures first and verifies least. The Mobile Number Verification API tells you whether the number is live, which operator and region it belongs to, and whether the name you hold matches the subscriber, giving you a strong, low-friction identity and reachability signal.

Use it to prioritise outreach, gate risky sign-ups and confirm that the number used for OTP belongs to the person you are onboarding.

Consent is part of the contract

Subscriber name matching uses personal data; capture the person's consent before running the match.

Benefits of the Mobile Number Verification API

Confirm a mobile number is active, who it is registered to and which network serves it.

Reachability

Know a number is live before you send links or call.

Fake sign-up control

Flag inactive, virtual or mismatched numbers.

Instant

Runs at form submission.

Low cost

Cheap enough for every lead and candidate.

Use cases

Mobile Number Verification API use cases

Where the Mobile Number Verification API is typically called, and what it settles there.

Candidate outreach

Verify numbers before sending consent and portal links.

Fintech sign-ups

Match the OTP number to the applicant.

Marketplace and gaming

Reduce multi-account abuse.

Collections and support

Keep contact databases clean.

How the Mobile Number Verification API works

Request and response details, environments and a ready-to-import collection are in the developer console at console.profiden.com.

01

Authenticate

Call with your organisation API key. Sandbox and production use the same contract.

02

Send the inputs

Mobile number as a JSON body. Optional fields sharpen the match.

03

We verify at source

Profiden queries the authoritative record, normalises the answer and logs the request.

04

Act on the result

A verification status plus the fields listed above, in the same response envelope as every other API.

Built for the DPDP Act 2023

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

Encryption in transit and at rest
Data processed in India
Per-request audit trail
Masked identifiers in responses

Mobile Number Verification API: frequently asked questions

What teams ask before adding the Mobile Number Verification API to their integration.

It depends on the subscriber data available for the number. The response states clearly when a match could not be attempted.

No. It is a silent check. Profiden's consent flows handle OTP separately when you need possession proof.

Related APIs

APIs that usually run alongside the Mobile Number Verification API, on the same key.

All APIs

Get access to the Mobile Number Verification API

Tell us your use case and expected volume. We set up the organisation, share per-call pricing and issue keys.