Employer Domain Verification w/o OTP

Overview:

The Employer Domain Verification Service is a robust tool designed to validate email addresses and provide insights into associated companies and accounts.

Key Features:

Email Validation: Instantly verify the authenticity of email addresses.
Company Details: Retrieve comprehensive information about associated companies, including registration data and financial specifics.
Account Insights: Access account-related details such as usernames and gibberish detection.

How it Works:

Simply provide an email address, and the service returns a verification report containing the status of the email, company details (if applicable), and account insights.

Use Cases:

Plug and Play: Disposable Inbox Check and Public Inbox Check baked-in to the product.
Fraud Prevention: Identify suspicious email addresses to prevent fraudulent activities.
Data Enrichment: Enhance customer profiles by appending company details to email addresses.
Account Security: Detect and mitigate the risk of gibberish or randomly generated usernames.

Benefits:

Accuracy: Real-time verification ensures accurate results.
Efficiency: Streamline operations with quick and reliable email validation.
Insightful Data: Gain valuable insights into companies and accounts associated with email addresses.

Get Started:

Check out our API Reference and start leveraging the Employer Domain Verification Service today to enhance data quality, improve security, and streamline processes.

EPFO Employment Data

The Employment Verification API suite empowers you to seamlessly verify employment information and validate email addresses, streamlining your verification processes.

API Endpoints in Employment Verification

EPFO Employment Data API
- Retrieves employment history from the EPFO database.
- URL: https://in.decentro.tech/v2/kyc/epfo/verification

Authentication

Client ID: Your unique client identifier.
Client Secret: Your confidential client secret key.
Module Secret: The secret key for the specific module.
Authentication Method: Basic Authentication

Making Requests

HTTP Method: POST
Content-Type: application/json

Request Body Structure

{
    "reference_id": "YOUR_REFERENCE_ID",  // Unique reference ID for the request
    "consent": true,                      // Indicates user consent
    "mobile": "USER_MOBILE_NUMBER",       // User's mobile number
    "uan": "USER_UAN_NUMBER"              // User's Universal Account Number (UAN)
}

Response Body Structure

{
    "decentroTxnId": "TRANSACTION_ID",
    "status": "SUCCESS",                      
    "responseCode": "RESPONSE_CODE",
    "message": "RESPONSE_MESSAGE",
    "data": {
        "uanList": [
            "UAN_NUMBER"
        ],
        "employmentData": [
            {
                "name": "EMPLOYEE_NAME",
                "guardianName": "GUARDIAN_NAME",
                "establishmentName": "EMPLOYER_NAME",
                "memberId": "MEMBER_ID",
                "dateOfJoining": "DATE_OF_JOINING"
            }
        ]
    },
    "responseKey": "success_employment_history"
}

Error Handling

The API returns appropriate error codes and messages in case of failures.
Consult the official documentation for detailed error handling information.

Additional Information

For comprehensive usage guidelines and error codes, refer to the official API documentation.
Ensure you have obtained the necessary credentials and permissions to access these APIs.

Important Note

Specific details for the Email Verification API(s) are currently unavailable. Please refer to the relevant documentation for their endpoints, request/response structures, and usage guidelines.

Quick References

Request Body

Field	Description	Type	Example
reference_id	Unique identifier for your request	String	`"your_unique_reference_id"`
consent	User's consent to access EPFO data	Boolean	`true`
mobile	User's mobile number linked to UAN	String	`"9999999999"`
uan	User's Universal Account Number (UAN)	String	`"1234567890123456"`

Response Body

Field	Description	Type	Example
decentroTxnId	Unique transaction ID assigned by Decentro	String	`"29C3CE3E0F854B4C831XXXXE0B9673"`
status	Overall status of the request	String	`"SUCCESS"`
responseCode	Decentro-specific response code	String	`"S00000"`
message	Descriptive message about the request outcome	String	`"Employment history fetched successfully."`
data	Object containing detailed employment information	Object	See below
responseKey	Key identifying the type of response data	String	`"success_employment_history"`

`data` Sub-object

Field	Description	Type	Example
uanList	List of retrieved UAN numbers	Array of Strings	`["1234567890123456"]`
employmentData	Array of objects containing employment details	Array of Objects	See below

`employmentData` Sub-object

Field	Description	Type	Example
name	Employee's full name	String	`"John Doe"`
guardianName	Employee's guardian's name	String	`"Jane Doe"`
establishmentName	Employer's name	String	`"Decentro Technologies Pvt Ltd"`
memberId	Employee's member ID in EPFO system	String	`"ABC123456"`
dateOfJoining	Date of joining the employment	String	`"2023-01-01"`

EPFO API Example

Request:

{
  "reference_id": "my-unique-reference",
  "consent": true,
  "mobile": "9876543210",
  "uan": "1234567890123456"
}

Response:

{
  "decentroTxnId": "29C3CE3E0F854B4C831XXXXE0B9673",
  "status": "SUCCESS",
  "responseCode": "S00000",
  "message": "Employment history fetched successfully.",
  "data": {
    "uanList": ["1234567890123456"],
    "employmentData": [
      {
        "name": "John Doe",
        "guardianName": "Jane Doe",
        "establishmentName": "Decentro Technologies Pvt Ltd",
        "memberId": "ABC123456",
        "dateOfJoining": "2023-01-01"
      }
    ]
  },
  "responseKey": "success_employment_history"
}

These tables provide a detailed breakdown of the request and response body structure for the Employment Verification API, making it easier to understand the expected data format and interactions.