Employment verification (EPFO)
EPF history, employee search and establishment checks.
Read a person's employer-wise EPF history by UAN, by PAN with their name, or by mobile. Confirm that a named employee appears in an establishment's EPFO records for a given month, and read an establishment's details with up to four months of contribution summaries.
- APIs
- 3 you can call, 1 more on request
- Consent
- Bound to every read
- Audit
- Every call in a hash-chained log
APIs in Employment verification (EPFO)
Every API shares the same key, error format and audit log. Each one is switched on for your account separately.
EPF employment history
Employer-wise EPF history by UAN, by PAN with employee_name, or by mobile. dob is optional.
POST /v1/employment/uanReferenceEmployee search in an establishment
Whether a named employee appears in an EPFO establishment's records for a month (MM/YYYY).
POST /v1/employment/employee-searchReferenceEPFO establishment details
Establishment details with contribution summaries for the last 1 to 4 months.
POST /v1/employment/establishmentReference
Available on request
We set these checks up for your account. Subscribe to the one you need and we will have it ready for you.
- On requestSubscribe
Employment history check
Builds a person's employment history from their mobile number and other details.
What teams use it for
Use cases for each Employment verification (EPFO) check. See how they combine with other products on the use cases page.
Employer-wise EPF history by UAN, PAN or mobile number.
- Verify a candidate’s past employers during hiring.
- Confirm a salaried borrower’s current employer and job stability.
- Find gaps or overlaps in employment that a CV does not show.
Whether a named employee appears in an EPFO establishment’s records for a month.
- Confirm an applicant works at the company they named.
- Verify salaried customers for employer-linked loans and payroll products.
Establishment details with recent contribution summaries.
- Check an employer is registered and paying EPF contributions.
- Assess the employer behind a salaried borrower.
- Gauge a supplier’s size and compliance during onboarding.
Employment history check
On requestBuilds an employment history from a mobile number and other details.
- Build an employment history when the candidate cannot share a UAN.
- Verify salaried status for loan applicants.
How you get Employment verification (EPFO)
From a new account to a live call in four steps.
Create your account
Sign up with your work email and create an app and its key. No API is active on a new account.
Pay and subscribe
Add money to your wallet, then subscribe to this API in Dashboard → API access. We switch it on for your account after your payment.
Make your first call
Once the API is activated, send the sample request to /v1/employment/uan with your key and read back the JSON.
Go live
Use a live key in production. Every call is checked against the APIs activated for you, drawn from your prepaid wallet, and recorded in a hash-chained audit trail.
Call epf employment history
The main call for this product. Use your own key once this API is switched on for your account.
Developer ready
Docs, MCP, and a prompt that does the work
Every product ships with an integration guide, an MCP server for AI agents, and a ready-to-paste prompt, so your first Employment verification (EPFO) call takes minutes, not days.
Integration guide
The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every Employment verification (EPFO) endpoint with a live sample you can run from the playground.
MCP server for AI agents
grappi-mcp exposes the API as agent tools over the same gateway, so every tool call keeps auth, consent, metering, and audit. Drop this into your MCP client config.
{
"mcpServers": {
"grappi": {
"command": "npx",
"args": ["grappi-mcp"],
"env": {
"GRAPPI_API_BASE": "https://grappi.ai",
"GRAPPI_API_KEY": "your-api-key"
}
}
}
}Prompt-ready integration
Paste this into your coding assistant or agent. It carries the real contract rules, so the generated client matches the gateway on the first try.
Integrate the Grappi Employment verification (EPFO) API into my app. Endpoints: - POST /v1/employment/uan (EPF employment history) - POST /v1/employment/employee-search (Employee search in an establishment) - POST /v1/employment/establishment (EPFO establishment details) Contract rules: send the key as a Bearer token in the Authorization header, treat all money as integer paise (100 paise is one rupee), send an Idempotency-Key on every POST, and branch on the error envelope error.code (handle 402 insufficient_balance, 403 api_not_activated, 403 consent_required, 422 validation_failed, 429 rate_limited, 503 api_unavailable). Write a small typed client for these endpoints plus one worked call, with validation and error handling, in my project's language.
Questions
How do I start?
Create an account and add money to your wallet. Then subscribe to this API in your dashboard and we switch it on for your account.
What comes with every API?
Auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail, identical across every API on the platform.
What do I need to go live?
Subscribe to the API in your dashboard and we switch it on for your account after your payment. The request and reply format is the same in test and in production.
Is this compliant for regulated use?
Reads are consent-bound and DPDP and RBI-AA aligned. Every call lands in a hash-chained audit trail, and every API is switched on for your account individually.