---
title: "Validate Aadhaar & Generate OTP API Reference"
description: "Validate a sender's Aadhaar number and trigger an OTP to the linked mobile for DMT Levin onboarding."
canonical: "https://eps.eko.in/docs/aadhaar-dmt-levin-validate"
---


> **Canonical URL:** https://eps.eko.in/docs/aadhaar-dmt-levin-validate
> 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.

# Validate Aadhaar & Generate OTP API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/payment/dmt-levin/sender/{customer_id}/aadhaar/otp`

Validate a sender's Aadhaar number and trigger an OTP to the linked mobile for DMT Levin onboarding.

Submits the sender's Aadhaar number via the DMT Levin channel to initiate OTP-based Aadhaar validation. The `otp_ref_id` from the sender's existing profile plus the Aadhaar number are required. Returns a new `otp_ref_id` for the validation session. Part of the Levin DMT sender onboarding flow.

> View product & pricing details: [Domestic Money Transfer (DMT)](https://eps.eko.in/products/dmt-api.md)

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| customer_id | integer | yes | Sender's mobile number. e.g. 9876543210 |

## 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 |
| aadhar | string | yes | 12-digit Aadhaar number of the sender. e.g. 123456789012 |
| otp_ref_id | string | yes | Reference ID returned from the Get Sender Info (or Create Sender) API for this customer. e.g. 73849201 |
| additional_info | string | yes | Additional info flag. Defaults to 1. e.g. 1 |

## 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.otp_ref_id | string | New OTP reference ID for the Aadhaar validation session. Pass to Validate Sender Aadhaar OTP. |
| data.mobile_hint | string | Masked mobile number to which the OTP was dispatched. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "aadhar": "123456789012",
  "otp_ref_id": "73849201",
  "additional_info": "1"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Aadhaar OTP dispatched successfully",
  "response_type_id": 1388,
  "data": {
    "otp_ref_id": "93847201",
    "mobile_hint": "******3210"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Invalid Aadhaar number |