E-Shram Verification API

Endpoint Overview

POST /api/v1/eshram/eshram-verification

Description

The E-Shram Verification API enables businesses to verify worker details using the UAN (Universal Account Number) and date of birth from India's E-Shram portal. This API provides access to verified worker information including full name, mobile number, and email address when available. E-Shram is India's first national database of unorganized workers, making this API essential for businesses that need to verify informal sector workers' identities and contact information.

This endpoint serves as a crucial bridge between businesses and the government's E-Shram database, enabling seamless verification of over 270 million registered unorganized workers across India. The API returns structured data that can be easily integrated into existing workflows for worker onboarding, payroll systems, and compliance reporting.

Key Benefits

Instant Verification: Get real-time access to verified worker details from the official E-Shram database

Government-Backed Data: Access authentic information directly from India's national unorganized worker registry

Comprehensive Details: Retrieve full name, mobile number, and email address in a single API call

Compliance Ready: Ensure regulatory compliance for businesses dealing with unorganized sector workers

Use Cases

Financial Services

Employment & Gig Economy

Government & Social Schemes

Loan Verification: Verify borrower identity and contact details for microfinance and lending platforms

Insurance Enrollment: Validate worker information for social security and insurance scheme enrollments

Digital Wallet KYC: Streamline know-your-customer processes for financial technology applications

Credit Assessment: Access verified contact information for credit scoring and risk assessment

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for API authentication (JWT format)
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
uan_no	String	Yes	Universal Account Number from E-Shram registration (12-digit number)
dob	String	Yes	Date of birth in YYYY-MM-DD format

Example Request

{
  "uan_no": "712261481234",
  "dob": "1997-10-01"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Contains the verification result data
data.client_id	String	Unique client identifier for the request
data.uan_no	String	The UAN number that was verified
data.dob	String	The date of birth used for verification
data.full_name	String	Complete name of the registered worker
data.mobile_no	String	Mobile number associated with the E-Shram account
data.email	String	Email address (may be empty if not provided during registration)
status_code	Integer	HTTP status code of the response
success	Boolean	Indicates whether the request was successful
message	String	Human-readable response message
message_code	String	Machine-readable message code

Example Successful Response

{
  "data": {
    "client_id": "eshram_dIzdvcxsgAzKHrCSsCMv",
    "uan_no": "712261481234",
    "dob": "1997-10-01",
    "full_name": "Abc",
    "mobile_no": "9508089988",
    "email": ""
  },
  "status_code": 200,
  "success": true,
  "message": "Success",
  "message_code": "success"
}

Possible Error Responses

Invalid UAN

Server Error

Authentication Error

{
  "status_code": 422,
  "success": false,
  "message": "Invalid UAN Number or DOB.",
  "message_code": "verification_failed"
}

This error occurs when the UAN number format is incorrect or doesn't exist in the E-Shram database.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and implement proper token rotation mechanisms

Never expose API credentials in client-side code or version control systems

Implement rate limiting to prevent abuse and ensure fair usage

Use HTTPS for all API communications to protect sensitive data in transit

Validate and sanitize UAN numbers before making API calls to prevent injection attacks

User Experience Guidelines

Provide clear error messages when UAN verification fails to guide users

Implement proper loading states during API calls to improve user experience

Cache successful verification results appropriately to reduce API calls

Offer fallback verification methods when E-Shram verification is unavailable

Ensure mobile number and email fields handle empty values gracefully in your UI

Code Samples

cURL

Python

Node.js

Related APIs

Aadhaar Verification API: Verify identity using Aadhaar numbers for comprehensive KYC processes
PAN Verification API: Cross-verify tax identification numbers for financial compliance
Bank Account Verification API: Validate bank account details for salary and payment processing
Voter ID Verification API: Additional identity verification for enhanced security checks

Compliance and Legal Considerations

This API accesses government data from the E-Shram portal and must be used in compliance with India's data protection laws and E-Shram terms of service. Ensure you have proper consent from workers before accessing their information. The API should only be used for legitimate business purposes such as worker verification, payroll processing, or scheme enrollment. Organizations must implement appropriate data security measures and retention policies when handling personal information retrieved through this API. Regular audits and compliance reviews are recommended to ensure adherence to evolving data protection regulations.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/eshram/eshram-verification' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "uan_no": "710061486223", "dob": "1997-01-01" }'

{ "data": { "client_id": "eshram_dIzdvcxsgAzKHrCSsCMv", "uan_no": "712261481234", "dob": "1997-10-01", "full_name": "Abc", "mobile_no": "9508089988", "email": "" }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Eshram Verification

E-Shram Verification API#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses