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.
Starts at ₹6.00 per verification · excl. GSTView Pricing
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.
What Can You Verify With Employee Verification API?
Key details returned across all Employee Verification API endpoints, ready to power your KYC and onboarding workflows.
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.
Employee Verification API Flow – Sample Request and Response
Send simple inputs. Get rich, verified data in seconds.
Verify employment history and employee identity by phone number via EPFO/UAN data.
Key Features
Everything you need to integrate and scale
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 API?
Primary Use Cases
How to Integrate
Get started in minutes with our simple integration process
- 1
Sign Up
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
Ready to build? Visit our AI hub for free plugins & tools to integrate faster.
- 5
Go Live
Start verifying employees in production.
Frequently Asked Questions
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?+
Sign up at ekostore.app/eps, verify your identity with your PAN and address details, load your wallet to test the verification APIs live, then integrate and go live.
What is EPS?+
EPS (Eko Platform Services) is the technology arm of Eko, providing the developer tools, AI tools, and APIs that power modern fintech integration.
What are the different ways to integrate with Eko EPS?+
Integrate in whichever way suits your stack: call the REST APIs directly, use our official SDKs (JavaScript and PHP) to skip request-signing boilerplate, or let an AI coding agent build the integration using our MCP server and skills. See the Developers and AI sections for each path.
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.
Is there a sandbox environment for testing?+
Yes. A full sandbox environment is available immediately on signup. You can test your integration end-to-end before going live — no commitment required.
What are the sandbox and production base URLs?+
Sandbox and production share the same paths and differ only by base URL: use https://staging.eko.in/ekoapi/v3 for UAT / Sandbox, and https://api.eko.in/ekoicici/v3 for Production. A common cause of failures is calling the sandbox/staging 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?+
Production API access may require your static public (server) IP to be whitelisted. If your calls work from Postman but fail or time out from your own server, share your static public IP with us so we can whitelist it.
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 — contact our team for detailed rates.
Recommended Solution Packs
Pre-bundled API stacks that include Employee Verification API, designed for common industry workflows.
Get API Access
Sign up now and start integrating in minutes. Our team will help you go live quickly.
- Sandbox access in minutes
- Dedicated integration support
- Comprehensive documentation
- Reliable, high-volume workflows
Get Employee Verification API Access
Get started in 10 minutes