Uan Check (v2)

Workforce & Assets

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

Turn a Universal Account Number into a verified emver timeline: employer names, joining and exit dates and the number of establishments. Confirm tenure claims and detect dual emver without waiting for HR departments to reply.

Endpoint

POST https://app.emver.io/api/sandbox/v1/uan-check-v2

Authorization: Bearer YOUR_API_KEY

Content-Type: application/json

Accept: application/json

Request parameters

Field	Type	Description
`uan_number` required	string	UAN Number

Example request

cURL

curl -X POST https://app.emver.io/api/sandbox/v1/uan-check-v2 \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "uan_number": "string"
}'

import requests

response = requests.post(
    "https://app.emver.io/api/sandbox/v1/uan-check-v2",
    headers={
        "Authorization": "Bearer YOUR_API_KEY",
        "Accept": "application/json",
    },
    json={
        "uan_number": "string"
    },
    timeout=60,
)
response.raise_for_status()
data = response.json()

const response = await fetch("https://app.emver.io/api/sandbox/v1/uan-check-v2", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
    "Accept": "application/json",
  },
  body: JSON.stringify({
      "uan_number": "string"
  }),
});

const data = await response.json();

$response = Http::withToken('YOUR_API_KEY')
    ->acceptJson()
    ->post('https://app.emver.io/api/sandbox/v1/uan-check-v2', {
        "uan_number": "string"
    });

$data = $response->json();

Replace YOUR_API_KEY and the placeholder values. Use the switch above to see production URLs.

Response

Structure · 200

{
  "status": INTEGER,
  "data": {
    "uan_number": STRING,
    "message": STRING
  }
}

Example · 200

{
  "status": 200,
  "data": {
    "uan_number": "string",
    "message": "string"
  }
}

Error · 4xx / 5xx

{
  "status": INTEGER,
  "message": STRING
}

See Errors & status codes for what each status means and which calls are billed.

About this API

Provident fund contributions leave an authoritative trail of where someone worked and for how long. The emver 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 emver signal available in India and the standard first step in emver's emver verification workflows, with manual verification reserved for gaps and discrepancies.

Consent. emver history is personal data; the candidate's consent is captured before the lookup and stored with the case.

Typical uses

Pre-employment verification. Validate tenure and employer names for every offer.
Moonlighting audits. Detect concurrent emver among existing staff.
Income and stability signals. emver continuity as an underwriting input.
Staffing and contract placement. Fast checks for high-volume deployment.

Questions

What if the candidate does not know their UAN?: 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.
Does it show salary?: No. The API returns establishments and dates, not contribution amounts or salary.
Are all employers covered?: 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.