Emver
Emver
Profiden+ Blog
Workforce & Assets

Employment History (EPFO) API

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.

Response
Real-time
Inputs
1 required
Consent
Recorded per request
Billing
Per successful call
POST /v1/epfo-employment-check
Sandbox · Production
  1. Your application sends

    • UAN number*
  2. Profiden API

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

  3. Verified with

    EPFO member records

  4. You receive

    • Member name
    • Number of establishments
    • Current employer
    • Employment history with dates
epfo-employment-check Full reference

What the Employment History (EPFO) API does

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 Profiden'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.

Benefits of the Employment History (EPFO) API

Retrieve a candidate's employment history from provident fund records using their UAN.

Days become seconds

Instant timeline instead of chasing previous employers for weeks.

Resume cross-check

Compare declared tenure with contribution records and flag gaps.

Dual employment detection

Overlapping establishments indicate concurrent jobs.

Cuts verification cost

Reserve manual employer calls for the cases that need them.

Use cases

Employment History (EPFO) API use cases

Where the Employment History (EPFO) API is typically called, and what it settles there.

Pre-employment verification

Validate tenure and employer names for every offer.

Moonlighting audits

Detect concurrent employment among existing staff.

Income and stability signals

Employment continuity as an underwriting input.

Staffing and contract placement

Fast checks for high-volume deployment.

How the Employment History (EPFO) 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

UAN 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

Employment History (EPFO) API: frequently asked questions

What teams ask before adding the Employment History (EPFO) API to their integration.

It appears on payslips and the provident fund portal. Profiden's candidate portal guides them to find it, and workflows can fall back to employer-contact verification 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 Profiden pairs this with manual verification.

Related APIs

APIs that usually run alongside the Employment History (EPFO) API, on the same key.

All APIs

Get access to the Employment History (EPFO) API

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