Corporate Signatory Details API

Endpoint Overview

POST /api/v1/corporate/signatory-details

Description

The Corporate Signatory Details API enables you to retrieve comprehensive information about authorized signatories and directors of a company registered with the Ministry of Corporate Affairs (MCA) in India. By providing a valid Corporate Identity Number (CIN), this API returns detailed information about all directors and signatories associated with the company, including their Director Identification Numbers (DIN), designations, appointment dates, and Digital Signature Certificate (DSC) registration status.

This API is essential for corporate due diligence, KYC verification processes, and compliance checks. It provides real-time access to official MCA records, ensuring that businesses can verify the authenticity of corporate signatories and maintain accurate records of company representatives for legal and regulatory purposes.

Key Benefits

Instant Verification: Retrieve real-time signatory information directly from MCA records without manual searches

Comprehensive Data: Access complete details including DIN/DPIN/PAN, designations, appointment dates, and DSC status

Enhanced Due Diligence: Streamline corporate KYC and onboarding processes with automated signatory verification

Regulatory Compliance: Ensure compliance with corporate governance requirements by maintaining up-to-date signatory records

Use Cases

Financial Services

Corporate Services

Legal & Compliance

Corporate Account Opening: Verify authorized signatories during business account opening to ensure only legitimate representatives are granted access

Loan Processing: Validate director information and signing authority before disbursing corporate loans or credit facilities

Investment Due Diligence: Confirm the identity and status of company directors before making investment decisions

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.app

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

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	JWT 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	Corporate Identity Number (CIN) of the company. Format: A 21-character alphanumeric code assigned by MCA (e.g., U12345MH1234PTC123456)

Example Request

{
    "id_number": "U12345MH1234PTC123456"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Container object for the response data
data.client_id	string	Unique identifier for the client request
data.company_id	string	The CIN of the company that was queried
data.results	array	Array of signatory/director objects containing detailed information
data.results[].din_dpin_pan	string	Director Identification Number (DIN), DPIN, or PAN of the signatory
data.results[].name	string	Full name of the director/signatory
data.results[].designation	string	Official designation of the signatory (e.g., Director, Managing Director)
data.results[].date_of_appointment	string	Date when the director was appointed (format: YYYY-MM-DD)
data.results[].whether_dsc_registered	string	Indicates whether a Digital Signature Certificate is registered
data.results[].expiry_date_of_dsc	string/null	Expiry date of the Digital Signature Certificate if registered, null otherwise
data.results[].surrendered_din	string	Indicates if the DIN has been surrendered (empty if not surrendered)
status_code	integer	HTTP status code of the response
success	boolean	Indicates whether the API request was successful
message	string/null	Additional message or error description (null on success)
message_code	string	Status message code (e.g., "success")

Example Successful Response

{
    "data": {
        "client_id": "mca_signatory_MarimHOxMfLlcmRnTvkc",
        "company_id": "U12345MH1234PTC123456",
        "results": [
            {
                "din_dpin_pan": "01234567",
                "name": "SHIRHATTI",
                "designation": "Director",
                "date_of_appointment": "2020-02-26",
                "whether_dsc_registered": "",
                "expiry_date_of_dsc": null,
                "surrendered_din": ""
            }
        ]
    },
    "status_code": 200,
    "success": true,
    "message": null,
    "message_code": "success"
}

Possible Error Responses

Invalid CIN

Unauthorized Access

Rate Limit Exceeded

{
    "data": null,
    "status_code": 400,
    "success": false,
    "message": "Invalid CIN format or CIN not found",
    "message_code": "invalid_input"
}

This error occurs when the provided CIN is either incorrectly formatted or does not exist in the MCA database. Verify the CIN format and ensure it is a valid 21-character corporate identity number.

Integration Best Practices

Security Recommendations

Secure Token Storage: Never expose JWT tokens in client-side code or version control systems. Store tokens securely in environment variables or secure credential management systems

Token Rotation: Implement a token refresh mechanism to regularly rotate JWT tokens and minimize security risks from token compromise

HTTPS Only: Always use HTTPS endpoints for API communication to ensure data encryption in transit

Input Validation: Validate and sanitize CIN inputs before making API calls to prevent injection attacks and ensure data integrity

Access Control: Implement role-based access control (RBAC) to limit which users or systems can access sensitive signatory information

User Experience Guidelines

Loading States: Display clear loading indicators when fetching signatory data, as API response times may vary based on the number of signatories

Error Handling: Provide user-friendly error messages that guide users on how to resolve issues (e.g., "Please verify the CIN and try again")

Data Presentation: Display signatory information in a clear, tabular format with proper labels for technical fields like DIN and DSC status

Empty States: Handle cases where no signatories are returned gracefully with appropriate messaging

Caching Strategy: Implement appropriate caching for signatory data to reduce API calls and improve application performance, while ensuring data freshness

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

This API provides access to public corporate records maintained by the Ministry of Corporate Affairs (MCA). Users must ensure compliance with applicable data protection laws including the Information Technology Act, 2000 and Digital Personal Data Protection Act, 2023 when processing and storing signatory information. The data should be used solely for legitimate business purposes such as KYC verification, due diligence, and compliance checks. Organizations must implement appropriate data security measures and ensure that access to signatory information is restricted to authorized personnel only. The API should not be used for unauthorized surveillance, harassment, or any purpose that violates individual privacy rights. Users are responsible for obtaining necessary consents where required and maintaining audit trails of data access for regulatory compliance.

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/corporate/signatory-details' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "id_number": "U12345MH1234PTC123456" }'

{ "data": { "client_id": "mca_signatory_MarimHOxMfLlcmRnTvkc", "company_id": "U12345MH1234PTC123456", "results": [ { "din_dpin_pan": "01234567", "name": "SHIRHATTI", "designation": "Director", "date_of_appointment": "2020-02-26", "whether_dsc_registered": "", "expiry_date_of_dsc": null, "surrendered_din": "" } ] }, "status_code": 200, "success": true, "message": null, "message_code": "success" }

Signatory Details

Corporate Signatory Details 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