Dual emver Check

Workforce & Assets

Detect concurrent emver from overlapping provident fund contributions.

Find out whether an employee or candidate is drawing salary from two employers at once. The check analyses provident fund contribution records for overlapping establishments and flags active moonlighting, with the periods and employers involved.

Endpoint

POST https://app.emver.io/api/sandbox/v1/dual-employment-check

Authorization: Bearer YOUR_API_KEY

Content-Type: application/json

Accept: application/json

Request parameters

Field	Type	Description
`u_a_n_number` required	string	UAN number
`current_employer_name` optional	string	Current employer name

Example request

cURL

curl -X POST https://app.emver.io/api/sandbox/v1/dual-employment-check \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "u_a_n_number": "string",
    "current_employer_name": "string"
}'

import requests

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

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

const data = await response.json();

$response = Http::withToken('YOUR_API_KEY')
    ->acceptJson()
    ->post('https://app.emver.io/api/sandbox/v1/dual-employment-check', {
        "u_a_n_number": "string",
        "current_employer_name": "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,
  "message": STRING,
  "data": {
    "dual_employment_detected": STRING,
    "overlapping_periods": STRING,
    "establishments_involved": STRING,
    "current_active_establishments": STRING
  }
}

Example · 200

{
  "status": 200,
  "message": "string",
  "data": {
    "dual_employment_detected": "string",
    "overlapping_periods": "string",
    "establishments_involved": "string",
    "current_active_establishments": "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

Remote work made dual emver common and hard to spot. This API looks at the contribution timeline behind a UAN and identifies periods where two or more establishments were contributing simultaneously, the clearest available evidence of concurrent emver.

Run it at hire and on a periodic basis for existing staff; emver workflows can schedule the sweep and raise cases only when an overlap appears.

Consent. emver records are personal data; the individual's consent is captured before the lookup and stored with the request.

Typical uses

Pre-joining checks. Confirm the candidate has exited their previous employer.
Workforce audits. Quarterly moonlighting sweeps for IT and services firms.
Staffing compliance. Ensure deployed contractors are not double-booked.
Lending. Detect undisclosed income sources or conflicting emver.

Questions

Can it detect freelance or cash work?: No. It detects concurrent formal emver through provident fund contributions. Informal work leaves no such record.
How recent is the data?: Contributions appear once employers file them, typically within a month of the salary period.