Mobile to EPFO API
Start from a mobile number and get every UAN linked to it, each with the employment history behind it, in one call.
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 to EPFO API does
The Mobile to EPFO API takes a 10-digit Indian mobile number and answers with the Universal Account Numbers (UANs) linked to it. For each UAN it returns the employment history in the same shape as the UAN Verification API: the employers, first and last contribution months, months with each, exit reasons, the member name and a summary with the total experience and the most recent employer.
Most candidates and loan applicants know their mobile number by heart but not their UAN. Starting from the number removes a form field people get wrong or leave blank, and shows when more than one UAN is linked, which can happen when a person was given a new UAN by a later employer.
Send the person’s name as well and each UAN’s employment block carries a name_match, exact, partial or mismatch with a score from 0 to 100, so you can tell whether the UANs found belong to the person you are checking.
How it works
- 1
Your server sends POST /universal/epf-uan-lookup with the 10-digit mobile number, the consent object and, if you have it, the person’s name.
- 2
The request is checked first: a number that is not 10 digits starting with 6, 7, 8 or 9, or a missing consent object, is refused with every problem listed before anything runs or is charged.
- 3
The number is checked against live records and the UANs linked to it come back in the same call with their employment histories, usually within about 5 seconds.
- 4
The result is stored in your VerifyAll account with a checkResultId; read it again, find it by your client_ref or download the PDF report.
Request and response
Mobile to EPFO API endpoints and fields
The main fields; the full reference with every field, error code and a cURL sample is in the dashboard docs.
| Endpoint | What it does |
|---|---|
| POST/universal/epf-uan-lookup | Find the UANs linked to a mobile number, with their employment |
Request fields
| Field | What it is |
|---|---|
| mobileRequired | The Indian mobile number linked to the UAN, 10 digits without +91. |
| consentRequired | obtained: true and a purpose of up to 200 characters, for the person the number belongs to. |
| nameOptional | The name the person gave; sets name_match on each UAN found. |
| client_refOptional | Your own reference, stored with the result (up to 100 characters). |
What the answer returns
| Field | What it is |
|---|---|
| mobile | The mobile number that was looked up. |
| uan_count | How many UANs are linked to the number. |
| uans[].uan | A UAN linked to the number (may be partly masked). |
| uans[].employment | That UAN’s employment history: member name, name_match, relation_name and remark; null when it could not be read. |
| uans[].employment.employers | Each establishment: name, ids, address, status, first and last contribution month, months and exit reason. |
| uans[].employment.summary | employer_count, total_experience_months and last_employer. |
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 to EPFO API features and capabilities
No UAN needed up front
Ask for the mobile number your candidate already gave you; the API finds the UANs linked to it.
Every linked UAN
uan_count and the uans list show when one number is linked to more than one UAN, each with its own history.
Employment history included
Each UAN comes with its employers, contribution months and summary, so one call can replace a lookup followed by a second check.
Name match per UAN
Each employment block carries its own name_match, so you can tell which UANs belong to the person you are checking.
Use cases
Where businesses use the Mobile to EPFO API
Candidate screening without a UAN
Run an employment check at the application stage using only the mobile number on the CV.
Salaried borrower checks
Confirm a loan applicant’s current employer from the mobile number they signed up with.
Finding the UAN for later checks
See which UANs are linked to the number, then ask the candidate to confirm the full UAN for your HR records and later UAN checks.
Spotting undeclared employment
See every employer linked to a candidate’s number, including ones left off their CV.
Industries
Coverage
Indian mobile numbers linked to a UAN, with the employment history of each UAN found. Numbers not linked to any UAN return no record.
Limitations to plan for
- Only UANs linked to that mobile number are found. If the person registered a different number on their account, this API will not find it.
- The UAN and member name may be partly masked. Ask the person for the full UAN if you need to store it.
- A number with no linked UAN answers record_not_found. The lookup ran, so it is charged like any completed check.
- Checks about a person need the consent object, and you keep the consent record.
Integration
How to integrate the Mobile to EPFO API
From a business account to your first live call.
Step 1
Create a business account on VerifyAll and get it approved, as for running checks in the dashboard.
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.
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.
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 to EPFO API
Tell us what you want to verify. We reply within one business day with access steps, Sandbox details and your API pricing.
View API documentation
The full reference for Mobile to EPFO 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 to EPFO API: frequently asked questions
Answers for teams planning an integration.
Still have questions? Our team is happy to help.
Contact SupportRelated APIs
UAN Verification API
LiveInstant answerSend a 12-digit UAN and get the person’s employment history back: every employer, the months with each and the most recent job.
View API detailsMobile Number Verification API
LiveInstant answerFind out whether an Indian mobile number is live, who it is registered to and which operator serves it, before you rely on it.
View API detailsBackground Verification API
LiveFinishes laterRun the background checks you choose on one person in a single request, and read back one report with an overall result and every check’s outcome.
View API details
All employment verification APIsRun Mobile to EPFO in the dashboard, without codeBrowse the API Marketplace
Start with the Mobile to EPFO API
Request access, build against the Sandbox, then go live with your Production key.