---
type: "product"
title: "Employee Verification API India | Workforce Background Checks"
description: "Verify employment history using phone number-based employee verification. Retrieve details such as employee name, PAN, UAN, Member ID, employer information, joining and exit dates, exit reason, and PF filing details for hiring, lending, staffing, and workforce onboarding workflows."
category: "verification"
canonical: "https://eps.eko.in/products/employee-verification-api"
---


> **Canonical URL:** https://eps.eko.in/products/employee-verification-api
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# Employee Verification API for Employment History Checks in India

Verify employment history using phone number-based employee verification. Retrieve details such as employee name, PAN, UAN, Member ID, employer information, joining and exit dates, exit reason, and PF filing details for hiring, lending, staffing, and workforce onboarding workflows.

_Digital employee identity verification_

To get started, fill the form at https://eps.eko.in/signup (with your name, mobile number and email) or call us at +919513181707

## Overview

The Employee Verification API enables organizations to verify employee identity and related details digitally during hiring and onboarding. It is designed to reduce hiring risk, improve compliance, and streamline workforce verification workflows.

## Features

- Employee Identity Verification: Verify employee identity details digitally as part of onboarding.
- Hiring Risk Reduction: Detect inconsistencies early to reduce impersonation and compliance risk.
- Automation Friendly: Integrates seamlessly into HRMS, ATS, and onboarding platforms.
- High-Volume Support: Designed to support large-scale hiring and verification needs.

## Who Should Use This

- Enterprises and large employers
- HR tech platforms
- Gig economy and staffing companies
- Organizations with compliance-driven hiring

## Use Cases

- Pre-employment verification
- Contractor and gig worker onboarding
- Workforce compliance checks
- Enterprise HR verification workflows

## What Can You Verify With Employee Verification API?

- **UAN Records** — List of UAN records associated with the employee's phone number. One entry per UAN.
- **Universal Account Number (UAN)** — Universal Account Number assigned to the employee by EPFO.
- **Basic Details** — Core identity details of the employee linked to this UAN.
- **Employee Name** — Full name of the employee as registered with EPFO.
- **Gender** — Gender of the employee.
- **Employee's DOB** — Date of birth of the employee in YYYY-MM-DD format.
- **Is Aadhaar Verified?** — Whether the employee's Aadhaar is linked and verified against this UAN.
- **Employment Details** — Employment record associated with this UAN entry.
- **Member Id** — PF Member ID for this employment record (state/region/establishment/account format).
- **Establishment Id** — EPFO establishment ID of the employer.
- **Establishment Name** — Name of the employer/establishment as registered with EPFO.
- **Joining Date** — Date the employee joined this establishment (YYYY-MM-DD).
- **Exit Date** — Date the employee exited this establishment (YYYY-MM-DD). Null if currently employed.
- **Leave Reason** — Reason for exit as recorded in EPFO (e.g., Resignation, Superannuation).
- **PAN Number** — PAN number linked to the employee.
- **Recent Employment Details** — Structured summary of the most recent employment, including EPFO health indicators and employer PF filing history.
- **Employee Details** — Latest employment record for the employee with EPFO flags.
- **Is Currently Employed?** — Whether the employee is currently active in this establishment per EPFO records.
- **Exit Date Marked** — Whether the employer has formally marked an exit date in EPFO.
- **Employee Name Match** — Whether the name in EPFO matches the name provided or derived from the phone lookup.
- **Epfo** — EPFO-level flags indicating data quality and filing health.
- **Recent** — Whether EPFO data for this employee was recently updated.
- **Name Unique** — Whether the employee's name appears uniquely in EPFO (no duplicates).
- **Pf Filings Details** — Whether PF filing details are available for this employee.
- **Employer Details** — Details of the most recent employer including setup date, ownership type, and monthly PF contribution history.
- **Setup Date** — Date the employer establishment was set up/registered with EPFO.
- **Ownership Type** — Ownership type of the establishment (e.g., Private, Government, Public Sector).
- **Employer Name Match** — Whether the resolved employer name matches the expected employer name.
- **PF Filing History** — Monthly PF contribution records filed by the employer. Each entry represents one wage month.
- **Wage Month** — The wage month for this PF filing entry (YYYY-MM format).
- **Total Amount** — Total PF amount contributed by the employer for this wage month.
- **Employees Count** — Number of employees covered under this PF filing for the wage month.

## API Preview — Employee Verification (Advance)

`POST /tools/kyc/advance-employment`

### Example inputs

| Field | Value |
| --- | --- |
| Phone | 9876543210 |

### Example outputs

| Field | Value |
| --- | --- |
| Universal Account Number (UAN) | 1001234567890 |
| Employee Name | Rajesh Kumar |
| Gender | Male |
| Employee's DOB | 1994-08-29 |
| Is Aadhaar Verified? | false |
| Member Id | MH/BOM/12345/000/0000001 |
| Establishment Id | MHBAN0012345000 |
| Establishment Name | Acme Pvt Ltd |
| Joining Date | 2019-04-01 |
| Exit Date | 2023-06-30 |
| Leave Reason | Resignation |
| PAN Number | ABCDE1234F |
| Universal Account Number (UAN) | 1001234567890 |
| Member Id | MH/BOM/12345/000/0000001 |
| Joining Date | 2019-04-01 |
| Exit Date | 2023-06-30 |
| Is Currently Employed? | false |
| Exit Date Marked | true |
| Employee Name Match | true |
| Recent | true |
| Name Unique | true |
| Pf Filings Details | true |
| Establishment Id | MHBAN0012345000 |
| Establishment Name | Acme Pvt Ltd |
| Setup Date | 2005-03-15 |
| Ownership Type | Private |
| Employer Name Match | true |
| Wage Month | 2023-05 |
| Total Amount | 1800 |
| Employees Count | 120 |

## Integration Steps

1. **[Sign Up](/console)** — Sign up in minutes with your mobile number (OTP verify).
2. **Verify Identity** — Complete your basic KYC with PAN and address details to verify your identity.
3. **Test APIs Live** — Load funds into your wallet and test the verification APIs live — evaluate before you integrate.
4. **[Integrate with AI](/ai)** — Ready to build? Visit our AI hub for free plugins & tools to integrate faster.
5. **Go Live** — Start verifying employees in production.

## FAQs

### What can be verified?
Employee identity details including name, ID documents, and related information can be verified digitally.

### Does it integrate with HRMS?
Yes, the API integrates seamlessly into HRMS, ATS, and onboarding platforms.

### How do I get started?
Four steps: **sign up** at the [developer console page](/console), verify your identity with PAN and address details, load your wallet to test the APIs live, then integrate and go live. Sandbox credentials are issued immediately — you can call your first endpoint before any paperwork clears.

### What is EPS?
**EPS (Eko Platform Services)** is the technology arm of Eko — the developer tools, AI tooling and APIs that power modern fintech integration, from money transfer and AePS to identity verification.

### What are the different ways to integrate with Eko EPS?
Three paths, pick whichever suits your stack:

- Call the **REST APIs** directly.
- Use our official **Node.js, Python, PHP, Go or Java SDKs** to skip request-signing boilerplate.
- Let an **AI coding agent** build it via our [MCP server and agent skills](/ai#install).

For multi-step flows (onboard a sender, *then* transfer) start from a [transaction-flow recipe](/recipe) rather than wiring single endpoints together yourself.

### How does API authentication work?
Each request carries your static `developer_key` header plus a per-request `secret-key` header — an **HMAC-SHA256** signature of the current timestamp, keyed by your access key. The access key itself is **never sent over the wire**. You receive UAT keys on signup and production keys after KYC.

The [How Authentication Works](/docs/how-auth-works) guide has the full signing recipe in five languages plus an **in-browser playground** that generates and verifies a real `secret-key` against your own access key.

### Why does my API call return 401 Unauthorized?
Authentication failed. For the known causes, the response body's `status` names the check that failed:

- `2483` — The developer_key is wrong.
- `2484` — The secret-key (signature) is wrong.
- `2485` — The secret-key-timestamp is more than 2 minutes older or newer than the server clock, or was reused from an earlier request.
- `2486` — The secret-key-timestamp is not in milliseconds (13 digits) — often seconds (10 digits).
- `2487` — The secret-key or secret-key-timestamp header is missing.

If your signature checks out in the [secret-key playground](/docs/how-auth-works#try-it-secret-key-playground) and you still get a `401`, make sure the base URL matches your keys (UAT vs production) and, in production, that your server's IP is whitelisted.

### Is there a sandbox environment for testing?
Yes. A full **sandbox** is available immediately on signup — test your integration end-to-end before going live, no commitment required. For offline work you can also run our [mock server](/ai#artifacts) (`npx -y @ekoindia/eps-mock-server`) and get canned responses with no network calls at all.

### What are the sandbox and production base URLs?
Sandbox and production share the same paths and differ **only** by base URL:

- UAT / Sandbox — `https://staging.eko.in/ekoapi/v3`
- Production — `https://api.eko.in/ekoicici/v3`

A common cause of failures is calling the sandbox URL with live credentials, or vice-versa — **make sure the base URL matches the keys you are using**.

### Do I need to whitelist my server IP?
It's optional. **IP whitelisting** is available for **production** access as an extra layer of security — share your **static public (server) IP** with us and we'll whitelist it.

### Can an AI coding agent build the integration for me?
Yes — that is the fastest path. Point your agent (Claude Code, Codex, Cursor, Copilot, …) at our **MCP server** and it can look up any endpoint, generate correctly-signed requests, and scaffold the integration in your own stack. Install it in [one step from the AI hub](/ai#install), or start from a [ready-made prompt](/ai#quick-start).

We also publish an **OpenAPI 3.1 spec**, a **Postman collection** and per-agent **context packs** (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`) so an agent has the ground truth instead of guessing.

### What response times can I expect?
Most verification APIs return in **real time with sub-second responses**, and 99th-percentile latency stays under two seconds across verification endpoints. Transaction APIs (DMT, AePS, BBPS) respond within seconds.

### Can the API handle high volumes?
Yes. The API is designed to handle **large-scale volumes** reliably without performance degradation.

### How is API usage billed?
Usage is billed **per successful API call** with no minimum commitment. Volume-based pricing tiers are available — see the [pricing calculator](/pricing) for indicative rates, or contact our team for a custom quote.

## API Endpoints

- [Employee Verification (Advance)](https://eps.eko.in/docs/advance-employment.md) (POST)

## API Documentation

- [Full developer docs](https://eps.eko.in/docs/advance-employment)

## Related Products

- [Mobile/OTP Verification](https://eps.eko.in/products/mobile-otp-verification-api): Send, verify & validate mobile OTPs with a signed proof token ([markdown](https://eps.eko.in/products/mobile-otp-verification-api.md))
- [PAN Verification](https://eps.eko.in/products/pan-verification-api): Full PAN identity fetch in <2 seconds ([markdown](https://eps.eko.in/products/pan-verification-api.md))
- [Bank Account Verification](https://eps.eko.in/products/bank-verification-api): Penny-drop bank account validation ([markdown](https://eps.eko.in/products/bank-verification-api.md))
- [GST Verification](https://eps.eko.in/products/gst-verification-api): GSTIN lookup & filing status ([markdown](https://eps.eko.in/products/gst-verification-api.md))
- [DigiLocker Integration](https://eps.eko.in/products/digilocker-api): Fetch notarised docs — Aadhaar, DL, marksheets, etc ([markdown](https://eps.eko.in/products/digilocker-api.md))

- [Site index](https://eps.eko.in/index.md): Full list of API products, industries, and solution packs