---
title: "Fetch PAN Details API Reference"
description: "Fetch the PAN holder's registered full name and category from the PAN number alone."
canonical: "https://eps.eko.in/docs/pan-fetch"
---


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

# Fetch PAN Details API Reference

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

Fetch the PAN holder's registered full name and category from the PAN number alone.

Fetch PAN is the lightest PAN lookup: pass only the PAN number and get back the registered full name, the holder category (person / company / firm …) and the PAN status. Unlike PAN Lite and PAN Advanced — which require the PAN number, holder name and date of birth to compute match flags — this endpoint needs no name or DOB, so use it when you have to *discover* the holder's name rather than verify one you already hold.

> 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 |
| client_ref_id | string | no | Unique reference ID per API call, generated by your system (max 20 characters). e.g. 2026010100123456789 |
| pan_number | string | yes | 10-character alphanumeric PAN identifier (5 letters, 4 digits, 1 letter). e.g. GGTPB7880Q |
| source | string | no | Origin of the request. Use 'API' for server-to-server calls. e.g. API |

## 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.upstream_rrn | string | Reference number of the lookup at the upstream source. |
| data.pan_no ⭐ | string | The PAN number submitted in the request. |
| data.fullname ⭐ | string | Full name registered against the PAN. |
| data.category ⭐ | string | PAN holder category, e.g. 'person', 'company', 'firm', 'trust', 'huf'. |
| data.status ⭐ | string | Outcome of the PAN lookup, e.g. 'success'. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "pan_number": "GGTPB7880Q",
  "source": "API"
}
```

## Example response

```json
{
  "response_status_id": 0,
  "data": {
    "upstream_rrn": "pan_ZLpBnmwapOwtixPUmijB",
    "pan_no": "GGTPB7880Q",
    "fullname": "YASHWANT BASNETT",
    "category": "person",
    "status": "success"
  },
  "response_type_id": 0,
  "status": 0
}
```