Skip to main content
VerifyAll logo
LiveInstant answerSandbox

Mobile Number Age Verification API

Send a mobile number and learn how long it has been in use, whether it is active or ported, its operator and circle, and whether it has been revoked.

The documentation opens in the VerifyAll dashboard after sign-in, for accounts with approved API access. New to the API? Start with the developer guide.

Overview

What the Mobile Number Age Verification API does

The Mobile Number Age Verification API tells you how long an Indian mobile number has been in use, together with whether it is active now, whether it has been ported to another network, its operator and telecom circle, and whether the number has been revoked: cut off, usually after misuse or a failed re-verification, and possibly since given to someone else.

Number age is a risk signal rather than an identity check. A number held for years reads very differently from one switched on a few days before sign-up, or one that was revoked and reissued. Fraud and credit teams use that difference at sign-up, before a loan is paid out, and before one-time passwords go to a number that has just been changed on an account.

The holder of the number does not need to do anything: no one-time password is sent. The answer comes back in the same call in VerifyAll’s standard JSON envelope, and the result is stored with a checkResultId and a PDF report, like every VerifyAll check.

How it works

  1. 1

    Your server sends POST /universal/mobile-age-verification with the 10-digit mobile number, the consent object and, if you like, a client_ref.

  2. 2

    The request is checked first: a number that is not a 10-digit Indian mobile, or a missing consent object, is refused with a list of every problem before anything runs or is charged.

  3. 3

    The number is checked against live records and the answer comes back in the same call, usually within a few seconds: the number age, whether it is active, ported or revoked, its operator and its circle.

  4. 4

    The result is stored with a checkResultId: read it again, find it by your client_ref and download the PDF report. A number with no record answers record_not_found; the lookup ran, so it is charged.

Request and response

Mobile number age API endpoints and fields

The main fields; the full reference with every field, error code and a cURL sample is in the dashboard docs.

Endpoints
EndpointWhat it does
POST/universal/mobile-age-verificationHow long a mobile number has been in use, and its active, ported and revoked status

Request fields

Mobile Number Age Verification API request fields
FieldWhat it is
mobileRequiredThe 10-digit Indian mobile number, starting 6 to 9 (a +91 or 0 prefix and spaces are removed).
consentRequiredobtained: true and a purpose of up to 200 characters, for the person the number belongs to.
client_refOptionalYour own reference, stored with the result (up to 100 characters).

What the answer returns

Mobile Number Age Verification API answer fields
FieldWhat it is
mobileThe mobile number checked.
number_ageHow long the number has been in use, as a range, for example "5 to 6 Years".
is_activeWhether the number is in use now.
is_portedWhether the number has been moved to another network.
operator / circleThe operator the number is on now and its telecom circle.
is_revokedWhether the number has been revoked (cut off), so that it may now belong to someone else.

Base URL https://api.verifyall.ai. Authenticate with the X-API-Key header (a va_sandbox_ or va_live_ key). Every answer carries data, status_code, success, message and message_code; checks add outcome, checkResultId, charged and charged_amount.

Key features

Mobile Number Age Verification API features and capabilities

  • How long the number has been in use

    A number activated days before sign-up stands out at once from one that has been in use for years.

  • Revoked numbers

    Shows whether the number was cut off and may now belong to someone other than the person who gave it to you.

  • Active, ported, operator and circle

    Context for the age: whether the number is in use, whether it has moved networks, and which operator and circle it is on now.

  • Nothing asked of the holder

    Only the number is needed. No one-time password is sent and the holder does not have to respond.

Use cases

Where businesses use the Mobile Number Age Verification API

  • Digital onboarding

    Flag sign-ups that use a number activated only days earlier, and ask for more before the account opens.

  • Lending

    Add number age to a borrower’s risk checks before a loan is approved or paid out.

  • Changes to an account’s mobile number

    Check a newly added number before one-time passwords and alerts start going to it.

  • Lead quality

    Separate long-held numbers from throwaway ones in inbound leads before sales time is spent on them.

Industries

Coverage

Indian 10-digit mobile numbers.

Limitations to plan for

  • Number age is a signal, not proof of identity: it says how long the number has been in use, not who holds it. Pair it with the Mobile Number Verification API or a PAN check.
  • A new number is not a sign of fraud on its own; people change numbers for ordinary reasons, so use the age as one input to a decision.
  • The age comes back as a range (for example "5 to 6 Years"), not an exact activation date. Fields the record does not hold come back as null.
  • A number with no record answers record_not_found. The lookup ran, so it is charged like any completed check.

Integration

How to integrate the Mobile Number Age Verification API

From a business account to your first live call.

  1. Step 1

    Create a business account on VerifyAll and get it approved, as for running checks in the dashboard.

  2. Step 2

    Request Developer API access under Developers in the dashboard: the APIs you need, your expected monthly volume and your use case. The VerifyAll team reviews it and shares the API Services Agreement.

  3. Step 3

    Once the agreement is signed and access is approved, create your Sandbox key and build against sample data. Sandbox calls are never charged.

  4. Step 4

    Create your Production key, recharge your wallet and switch the key in your code: the endpoint and fields stay the same.

Get started

Request access to the Mobile Number Age Verification API

Tell us what you want to verify. We reply within one business day with access steps, Sandbox details and your API pricing.

Tell us about your integration

Tell us what you want to verify and how many checks you expect. Our team replies within one business day with access steps, Sandbox details and your API pricing.

We use these details only to reply to your request. See our privacy policy.

  • Contact sales

    Questions on volumes, onboarding or the API agreement.

    Contact sales
  • View API documentation

    The full reference for Mobile Number Age Verification API (endpoints, fields, errors, cURL) opens in the dashboard once your access is approved.

    Open the docs (sign-in)
  • Create a business account

    API keys are issued to an approved business account. Sign up, then request access under Developers.

    Create account

Pricing

Production calls are charged per check from your prepaid VerifyAll wallet, at your account’s API price; GST is added separately when you recharge. Sandbox calls are never charged. Your API prices are shown in the dashboard once access is approved. How pricing works

Already have a business account? Sign in to request access

Mobile Number Age Verification API: frequently asked questions

Answers for teams planning an integration.

Still have questions? Our team is happy to help.

Contact Support

All other verifications APIsRun Mobile number age in the dashboard, without codeBrowse the API Marketplace

Start with the Mobile Number Age Verification API

Request access, build against the Sandbox, then go live with your Production key.