Director Mobile

Endpoint Overview

POST /api/v1/corporate/director-phone

Description

This API endpoint retrieves the mobile phone number of a company director by providing their Director Identification Number (DIN). It enables secure and efficient verification of director contact information directly from official records, eliminating the need for manual verification processes.

Key Benefits

Instant verification of director mobile numbers without manual intervention

Reduces fraud risk by accessing official director contact information

Streamlines corporate KYC and due diligence processes

Enables automated director verification workflows

Use Cases

Banking & Finance

Corporate Compliance

Business Services

Verify director contact details during corporate account opening

Authenticate director identity during high-value transactions

Validate director information for corporate loan applications

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 (JWT format)
Content-Type	Yes	Application/json

Request Body

Parameter	Type	Required	Description
id_number	String	Yes	Director Identification Number (DIN) of the company director

Example Request

{
    "id_number": "00000000"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Container for the response data
data.client_id	String	Unique identifier for the API request
data.din_number	String	The DIN number that was provided in the request
data.phone_number	String	Mobile number of the director associated with the provided DIN
status_code	Integer	HTTP status code indicating the result of the request
success	Boolean	Indicates whether the API call was successful
message	String or null	Additional information about the response (null if successful)
message_code	String	Code indicating the type of response message

Example Successful Response

{
    "data": {
        "client_id": "director_phone_oxjmjVHbVouynMCmjptC",
        "din_number": "00000000",
        "phone_number": "+91900000000000"
    },
    "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_input"
}

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

Integration Best Practices

Security Recommendations

Store API keys securely and never expose them in client-side code

Implement proper error handling to prevent information leakage

Use HTTPS for all API communications

Rotate JWT tokens periodically and implement token expiration

User Experience Guidelines

Implement proper loading states while waiting for API response

Display clear error messages to users when verification fails

Cache successful responses when appropriate to improve performance

Provide clear instructions for users when manual verification is needed

Code Samples

cURL

Python

Node.js

Related APIs

Company Director Verification: Verify the identity and details of company directors

Corporate PAN Verification: Verify company PAN details for corporate entities

Company Information Lookup: Retrieve comprehensive information about registered companies

Compliance and Legal Considerations

This API accesses personal information of company directors and is subject to data privacy regulations. Ensure you have appropriate consent and legal basis for accessing this information. Usage of this data must comply with applicable privacy laws including but not limited to GDPR and local data protection regulations. The data should only be used for legitimate business purposes such as KYC, fraud prevention, or regulatory compliance.

{ "data": { "client_id": "director_phone_oxjmjVHbVouynMCmjptC", "din_number": "00000000", "phone_number": "+91900000000000" }, "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 ********************

Director Mobile

Director Mobile#

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

Director Mobile

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples