Integrate end to end on free demo hits — pay only when you go live.Free demo hits. Pay when you go live.
Request access
Turn a Universal Account Number into a verified employment timeline: employer names, joining and exit dates and the number of establishments. Confirm tenure claims and detect dual employment without waiting for HR departments to reply.
Your application sends
emver API
Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.
Verified with
EPFO member records
You receive
Provident fund contributions leave an authoritative trail of where someone worked and for how long. The Employment History API reads that trail from the UAN and returns the establishments and dates, giving you an instant, document-free cross-check of the resume before slower employer-contact verification begins.
It is the fastest employment signal available in India and the standard first step in emver's employment verification workflows, with manual verification reserved for gaps and discrepancies.
Consent is part of the contract
Employment history is personal data; the candidate's consent is captured before the lookup and stored with the case.
Retrieve a candidate's employment history from provident fund records using their UAN.
Instant timeline instead of chasing previous employers for weeks.
Compare declared tenure with contribution records and flag gaps.
Overlapping establishments indicate concurrent jobs.
Reserve manual employer calls for the cases that need them.
Where the Employment History (EPFO) API is typically called, and what it settles there.
Validate tenure and employer names for every offer.
Detect concurrent employment among existing staff.
Employment continuity as an underwriting input.
Fast checks for high-volume deployment.
Request and response details, environments and a ready-to-import collection are in the developer console.
Call with your organisation API key. Sandbox and production use the same contract.
UAN number as a JSON body. Optional fields sharpen the match.
emver queries the authoritative record, normalises the answer and logs the request.
A verification status plus the fields listed above, in the same response envelope as every other API.
Privacy and security built in
Consent recorded · Payloads not retained beyond your retention window · Every request traceable
FAQ
What teams ask before adding the Employment History (EPFO) API to their integration.
It appears on payslips and the provident fund portal. Prompt the user for it in your flow, or fall back to the employer-contact verification API if none exists.
No. The API returns establishments and dates, not contribution amounts or salary.
Employers registered for provident fund, which includes most organisations above the statutory headcount. Small or exempt employers may not appear, which is why emver pairs this with manual verification.
Usually called with the Employment History (EPFO) API, on the same key.
Identity & KYC
Validate a PAN, match the name and confirm it is active with the tax department.
Business & KYB
Validate a Tax Deduction Account Number and resolve the deductor.
Banking & Credit
Consent-based credit score and report for lending and financial-role screening.
Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.