---
title: "PAN Lite API Reference"
description: "Instant PAN validation with name and DOB match scores plus Aadhaar seeding status."
canonical: "https://eps.eko.in/docs/pan-lite"
---


> **Canonical URL:** https://eps.eko.in/docs/pan-lite
> 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.

# PAN Lite API Reference

`POST https://staging.eko.in/ekoapi/v3/tools/kyc/pan-lite`

Instant PAN validation with name and DOB match scores plus Aadhaar seeding status.

PAN Lite performs a lightweight synchronous PAN verification. Supply the PAN number, holder name, and date of birth; the API returns match flags for name and DOB, the PAN activation status code, and whether the PAN is seeded (linked) with Aadhaar. Note: the name field in the response reflects the name you submitted, not the registered name on the PAN record — use PAN Advanced for the registered name.

> View product & pricing details: [PAN Verification](https://eps.eko.in/products/pan-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 |
| pan_number | string | yes | 10-character alphanumeric PAN identifier (5 letters, 4 digits, 1 letter). e.g. ABCDE1234F |
| name | string | yes | Individual's name to match against PAN records. e.g. Rajesh Kumar |
| dob | string | yes | Date of birth in YYYY-MM-DD format. e.g. 1994-08-29 |

## 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.pan | string | The PAN number submitted in the request. |
| data.name | string | Name as submitted in the request (not the registered name on the PAN card). |
| data.dob | string | Date of birth as submitted in the request (YYYY-MM-DD). |
| data.name_match ⭐ | string | Whether the submitted name matches the PAN record. Values: 'Y' (match), 'N' (no match), or null (unavailable). |
| data.dob_match ⭐ | string | Whether the submitted date of birth matches the PAN record. Values: 'Y' (match), 'N' (no match), or null (unavailable). |
| data.pan_status ⭐ | string | Granular PAN activation status code. E: Valid, EC: Valid (Acquisition), N: Non-existent, X: Deactivated, F: Fake, D: Deleted, EA: Valid (Amalgamation), ED: Valid (Death), EI: Valid (Dissolution), EL: Valid (Liquidated), EM: Valid (Merger), EP: Valid (Partition), ES: Valid (Split), EU: Valid (Under Liquidation) |
| data.status ⭐ | string | High-level PAN validity: 'VALID' or 'INVALID'. |
| data.aadhaar_seeding_status ⭐ | string | Aadhaar-PAN seeding/linking status. Values: 'Y' (seeded), 'R' (registered but not confirmed), 'NA' (not seeded), or null. |
| data.aadhaar_seeding_status_desc | string | Human-readable description of the Aadhaar-PAN linkage status. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "pan_number": "ABCDE1234F",
  "name": "Rajesh Kumar",
  "dob": "1994-08-29"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "PAN verification successful",
  "response_type_id": 1388,
  "data": {
    "pan": "ABCDE1234F",
    "name": "Rajesh Kumar",
    "dob": "1994-08-29",
    "name_match": "Y",
    "dob_match": "Y",
    "pan_status": "E",
    "status": "VALID",
    "aadhaar_seeding_status": "Y",
    "aadhaar_seeding_status_desc": "Aadhaar is linked to PAN"
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | Invalid or non-existent PAN |
| 400 | Missing required parameter |