POSTDIN Verification

Verify Director Identification Numbers (DIN) against MCA records — returns director name, DIN status, designation, and associated company information.

POST/tools/kyc/din-verification

Read-only: Changes nothing; only returns data.
₹2.04 + GST / verification: Charged per successful call; failed calls are free.

Warning

The UAT environment is not available for this API — requests to https://staging.eko.in/ekoapi/v3 return an error response. Test it in Production.

The DIN Verification API lets you validate a Director Identification Number (DIN) against Ministry of Corporate Affairs (MCA) records in real time. It returns the director's full name, current DIN status (Active / Deactivated / Surrendered), designation, and the associated company name. Use it for corporate KYB onboarding, director background checks, vendor due diligence, lending to corporate borrowers, and compliance workflows that require authoritative director-identity validation.

Request

Body parameters

Field	Type	Required	Description
`initiator_id`	string	required	Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729
`client_ref_id`	string	optional	Unique reference ID per API call, generated by your system (10–20 characters; 10 recommended). The SDKs generate one for every non-GET call when you don't.e.g. 2026010100123456789
`din_number`	string	required	The 8-digit Director Identification Number (DIN) assigned by the Ministry of Corporate Affairs to the individual director.e.g. 06731826

initiator_idstringRequired

Registered mobile number of the API user (see Platform Credentials).

example: 9962981729

client_ref_idstringoptional

Unique reference ID per API call, generated by your system (10–20 characters; 10 recommended). The SDKs generate one for every non-GET call when you don't.

example: 2026010100123456789

din_numberstringRequired

The 8-digit Director Identification Number (DIN) assigned by the Ministry of Corporate Affairs to the individual director.

example: 06731826

These headers authenticate and sign every request. See How Auth Works for details.

Field	Type	Required	Description
`developer_key`	string	required	Static API key issued to your account after KYC.
`secret-key`	string	required	Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
`secret-key-timestamp`	string	required	Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
`content-type`	string	required	application/jsone.g. application/json

developer_keystringRequired

Static API key issued to your account after KYC.

secret-keystringRequired

Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

secret-key-timestampstringRequired

Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

content-typestringRequired

application/json

example: application/json

Responses

statusnumber
Primary success indicator (0 = success).
messagestring
Human-readable response / error message.
response_status_idnumber
UI display hint only (-1/0 success, 1 failure, 2 initiated, 3 refund initiated, 4 refunded). Never branch on it — use `status` (and `tx_status` for financial APIs), or `response_type_id` where documented.
response_type_idnumber
A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobject
API-specific response payload.
- dinstring
  The DIN submitted in the request, echoed back for confirmation.
- director_namestring
  Full legal name of the director as registered with MCA.
- din_statusstring
  Current status of the DIN as recorded by MCA — e.g. Active, Deactivated, Surrendered, Disqualified.
- designationstring
  Role or designation of the director as filed with MCA.
- company_namestring
  Name of the company with which the director is associated, as recorded in MCA records.

POSTDIN Verification

Request

Body parameters

Responses

Next steps

Related