DIN Verification API

Endpoint Overview

POST /api/v1/corporate/din

Description

The DIN Verification API allows you to retrieve comprehensive details associated with a Director Identification Number (DIN) in India. This endpoint provides information about the DIN holder including personal details, address information, and companies with which the director is associated. The API is designed to help organizations verify director identities for regulatory compliance, due diligence, and corporate governance purposes.

Key Benefits

Instant verification of DIN authenticity and current status

Access to comprehensive director information from official records

Streamlined corporate governance and regulatory compliance processes

Reduction in manual verification efforts and associated costs

Use Cases

Financial Services

Corporate Compliance

Legal Services

Verify director identities during corporate account opening

Conduct due diligence for corporate lending decisions

Validate board member credentials for investment evaluations

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 authentication. Format: `Bearer {your_jwt_token}`
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
id_number	String	Yes	The Director Identification Number (DIN) to be verified

Example Request

{
    "id_number": "0000000"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Contains the DIN verification details
data.client_id	String	Unique identifier for the API request
data.din_number	String	The DIN number that was verified
data.father_name	String	Father's name of the DIN holder
data.full_name	String	Full name of the DIN holder
data.dob	String	Date of birth of the DIN holder in YYYY-MM-DD format
data.nationality	String	Nationality code of the DIN holder (e.g., "IN" for India)
data.present_address	String	Current residential address of the DIN holder
data.permanent_address	String	Permanent address of the DIN holder
data.email	String	Email address of the DIN holder
data.pan_number	String	PAN (Permanent Account Number) of the DIN holder, if available
data.companies_associated	Array	List of companies with which the director is associated
data.status	String	Status of the DIN verification process
status_code	Integer	HTTP status code of the response
success	Boolean	Indicates if the API request was successful
message	String	Additional information about the response (null if no message)
message_code	String	Code indicating the type of message

Example Successful Response

{
    "data": {
        "client_id": "corporate_din_hYzkWdzfBnNVooebzfgQ",
        "din_number": "0000000",
        "father_name": "  CHANDWANI",
        "full_name": "  CHANDWANI",
        "dob": "1964-03-14",
        "nationality": "IN",
        "present_address": "SONA MAHAL APT",
        "permanent_address": "",
        "email": "aaaa.abcd@gmail.com",
        "pan_number": null,
        "companies_associated": [],
        "status": "success"
    },
    "status_code": 200,
    "success": true,
    "message": null,
    "message_code": "success"
}

Possible Error Responses

Invalid DIN

Authentication Error

{
    "data": null,
    "status_code": 400,
    "success": false,
    "message": "Invalid DIN number provided",
    "message_code": "invalid_din"
}

This error occurs when the provided DIN number is not in the correct format or does not exist.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and never expose them in client-side code

Implement token refresh mechanisms to handle token expiration

Use HTTPS for all API communications to ensure data encryption

Implement proper error handling to avoid exposing sensitive information

User Experience Guidelines

Implement caching strategies to improve response times for frequently verified DINs

Display verification results in a user-friendly format, highlighting key director information

Provide clear error messages to end-users when verification fails

Include timestamp of verification to indicate data freshness

Code Samples

cURL

Python

Node.js

Related APIs

Company Verification API - Retrieve comprehensive details about registered companies

PAN Verification API - Verify Permanent Account Number details of individuals and entities

GST Verification API - Validate and retrieve details associated with GST registration numbers

Compliance and Legal Considerations

The DIN Verification API accesses official government records. Ensure you have proper consent and legal basis for accessing this information. Usage of this API should comply with relevant data protection regulations, including but not limited to the Information Technology Act and potential Personal Data Protection laws in India. Verify that your use case is compliant with the terms of service provided by Surepass.

{ "data": { "client_id": "corporate_din_hYzkWdzfBnNVooebzfgQ", "din_number": "0000000", "father_name": " CHANDWANI", "full_name": " CHANDWANI", "dob": "1964-03-14", "nationality": "IN", "present_address": "SONA MAHAL APT", "permanent_address": "", "email": "aaaa.abcd@gmail.com", "pan_number": null, "companies_associated": [], "status": "success" }, "status_code": 200, "success": true, "message": null, "message_code": "success" }

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

DIN

DIN 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