---
title: "Validate Sender Aadhaar OTP API Reference"
description: "Verify the Aadhaar OTP to complete DigiKhata sender Aadhaar e-KYC."
canonical: "https://eps.eko.in/docs/ppi-digikhata-verify-aadhaar-otp"
---


> **Canonical URL:** https://eps.eko.in/docs/ppi-digikhata-verify-aadhaar-otp
> 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 Sender Aadhaar OTP API Reference

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

Verify the Aadhaar OTP to complete DigiKhata sender Aadhaar e-KYC.

Validates the OTP dispatched during Generate Sender Aadhaar OTP. On success the Aadhaar identity is confirmed and the flow proceeds to PAN validation (Pan Number Required).

> View product & pricing details: [PPI Wallet](https://eps.eko.in/products/ppi-api.md)

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| customer_id | string | yes | Sender's 10-digit mobile number. e.g. 8617567988 |

## 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 |
| otp | integer | no | OTP received from Generate Sender Aadhaar OTP. e.g. 654321 |
| otp_ref_id | integer | yes | otp_ref_id received from Generate Sender Aadhaar OTP. e.g. 66748392 |

## 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.application_id | string | KYC application identifier, when issued. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "otp": 654321,
  "otp_ref_id": 66748392
}
```

## Example response

```json
{
  "response_status_id": 0,
  "data": {
    "application_id": ""
  },
  "response_type_id": 2147,
  "message": "Pan Number Required",
  "status": 0
}
```