EPFO Employment & Payroll Verification API
Cut employee background verification delays from 3–4 business days down to 15–35 seconds with a strict 40-second timeout guarantee. Direct digital validation against official EPFO member contribution registries.
Outcome & Chargeability Reference
Predictable developer error responses with zero charges on downstream timeouts or validation rejections.
| HTTP Status | Outcome Code | Description | Billing Policy |
|---|---|---|---|
| 200 OK | SUCCESS | Profile and complete employment history retrieved successfully. | Chargeable |
| 404 Not Found | NOT_FOUND | Valid 12-digit UAN was queried against EPFO registry but no record exists. | Chargeable (Registry Queried) |
| 400 / 422 | INVALID_INPUT | Payload validation failed (e.g. UAN is not exactly 12 digits). | ₹0 (Free / No Charge) |
| 429 Too Many Req | RATE_LIMITED | Client burst rate limit exceeded; temporary throttle. | ₹0 (Free / No Charge) |
| 503 Unavailable | TIMEOUT | Upstream EPFO portal did not respond within strict 40s SLA threshold. | ₹0 (Free / No Charge) |
Standardized Response Format
Standard JSON response schema returning complete establishment contribution dates and dual-employment indicators.
// Sample Request POST https://www.aspassociates.in/api/v1/gateway/uan-employment-v3 Authorization: Bearer <YOUR_API_KEY> Content-Type: application/json { "uan_number": "100439846216", "realtime_data": true } // Sample Response (200 OK — Typical TAT: 22s) { "outcome": "SUCCESS", "profile_details": { "name": "RAJESH KUMAR", "gender": "M", "uan_allotment_date": "15-JUN-2015", "father_or_husband_name": "RAMESH KUMAR", "registered_on_portal": "YES", "mobile_number": "******3210", "email_id": "raj*********@gmail.com" }, "employment_history": [ { "member_id": "MHBAN00461350003050137", "establishment_name": "TECH SOLUTIONS PVT LTD", "joining_date": "2015-06-20", "exit_date": "2021-12-15" } ] }
Employment Verification Questions
How does this compare to manual background verification?
Legacy agencies manually email HR departments, taking 3 to 4 business days. ASP Associates queries official digital records in under 60 seconds, eliminating origination drop-offs for digital lenders and hiring teams.
How do you prevent moonlighting / dual employment fraud?
Our intelligent engine scans the start and exit dates across all registered establishment IDs under the candidate's UAN, immediately flagging active parallel payroll contributions.
Is candidate consent mandatory?
Yes. In strict alignment with the DPDP Act 2023, every API request requires a verified candidate consent parameter before accessing records.
Can we integrate this directly into our existing ATS / HRMS?
Yes. Our REST API integrates with any system in under 15 minutes. We provide standard Node.js, Python, and cURL snippets.