---
title: "DIN Verification API Reference"
description: "Verify Director Identification Numbers (DIN) against MCA records — returns director name, DIN status, designation, and associated company information."
canonical: "https://eps.eko.in/docs/din-verification"
---


> **Canonical URL:** https://eps.eko.in/docs/din-verification
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# DIN Verification API Reference

`POST https://staging.eko.in/ekoapi/v3/tools/kyc/touras/din-verification`

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

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.

> View product & pricing details: [DIN Verification](https://eps.eko.in/products/din-verification-api.md)

## Body parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| initiator_id | string | yes | Registered mobile number of the API user (see Platform Credentials). e.g. 9962981729 |
| user_code | string | yes | User code of the retailer/agent the service is run for. e.g. 20810200 |
| client_ref_id | string | no | Unique reference id per API call, generated by your system. e.g. REQ-20260101-001 |
| din_number | string | yes | The 8-digit Director Identification Number (DIN) assigned by the Ministry of Corporate Affairs to the individual director. e.g. 06731826 |

## Headers

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

## Response

⭐ marks fields highlighted as verifiable.

| Field | Type | Description |
| --- | --- | --- |
| status | number | Primary success indicator (0 = success). |
| message | string | Human-readable response / error message. |
| response_status_id | number | Granular status id; see the shared error-codes table. |
| response_type_id | number | A unique id for every possible response shape (success or error) — useful for client logic branching and analytics. |
| data | object | API-specific response payload. |
| data.din ⭐ | string | The DIN submitted in the request, echoed back for confirmation. |
| data.director_name ⭐ | string | Full legal name of the director as registered with MCA. |
| data.din_status ⭐ | string | Current status of the DIN as recorded by MCA — e.g. Active, Deactivated, Surrendered, Disqualified. |
| data.designation ⭐ | string | Role or designation of the director as filed with MCA. |
| data.company_name ⭐ | string | Name of the company with which the director is associated, as recorded in MCA records. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "din_number": "06731826"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "DIN verification successful",
  "response_type_id": 1388,
  "data": {
    "din": "06731826",
    "director_name": "Abhishek Sagar",
    "din_status": "Active",
    "designation": "Director",
    "company_name": "Eko India Financial Services Pvt Ltd"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Invalid or malformed DIN (not 8 digits) |
| 200 | DIN not found in MCA records |
| 403 | Authentication failure — invalid secret-key or timestamp |
| 200 | Missing required body parameter (din_number) |