---
title: "Bulk PAN Verification API Reference"
description: "Async batch PAN verification — submit multiple PANs in one call and poll for results via the Bulk PAN Status API."
canonical: "https://eps.eko.in/docs/pan-bulk-verify"
---


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

# Bulk PAN Verification API Reference

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

Async batch PAN verification — submit multiple PANs in one call and poll for results via the Bulk PAN Status API.

Bulk PAN Verification accepts an array of PAN entries (each with a PAN number and optional name) in a single POST request and returns a reference_id for tracking. Because verification runs asynchronously, callers must subsequently poll the Bulk PAN Verification Status API with the returned reference_id to retrieve individual results. Suited for high-volume operations such as employee on-boarding, merchant KYC batches, or overnight reconciliation runs.

> 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. e.g. REQ-20260101-001 |
| entries | array | yes | Array of PAN verification entries. Each entry contains a PAN number (required), name (optional), user_code (optional), and source (optional, defaults to 'API'). e.g. [object Object],[object Object] |

## 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.reference_id | number | Unique identifier for the submitted batch. Pass this to the Bulk PAN Verification Status API to retrieve individual PAN results once processing is complete. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "REQ-20260101-001",
  "entries": [
    {
      "pan": "ABCPV1234D",
      "name": "John",
      "source": "API"
    },
    {
      "pan": "ABCPV1234L",
      "name": "John Doe",
      "source": "API"
    }
  ]
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Bulk PAN verification request accepted. Poll status API for results.",
  "response_type_id": 1388,
  "data": {
    "reference_id": 123456
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 400 | Empty or missing entries array |
| 400 | Malformed PAN in one or more entries |