---
title: "Fetch GSTINs by PAN API Reference"
description: "Retrieve all GSTINs linked to a given PAN — with their state and status — in a single API call."
canonical: "https://eps.eko.in/docs/gstin-with-pan"
---


> **Canonical URL:** https://eps.eko.in/docs/gstin-with-pan
> 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 GSTINs by PAN API Reference

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

Retrieve all GSTINs linked to a given PAN — with their state and status — in a single API call.

The GSTIN with PAN API accepts a PAN (Permanent Account Number) and returns a list of all GSTIN registrations associated with that PAN across every Indian state and union territory. Each entry in the list includes the GSTIN, its active/inactive status, and the state of registration. Ideal for identifying all GST registrations of a counterparty, detecting multi-state business presence, and de-duplicating vendor or merchant records during onboarding.

> View product & pricing details: [GST Verification](https://eps.eko.in/products/gst-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 | string | yes | 10-character alphanumeric PAN of the business or individual (5 letters, 4 digits, 1 letter). e.g. ABCDE1234F |

## 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 submitted in the request, echoed back for reference. |
| data.gstin_list ⭐ | array | List of all GSTIN registrations linked to the given PAN. Each element represents one GST registration across a state. |
| data.gstin_list.gstin ⭐ | string | A GSTIN number associated with the PAN. |
| data.gstin_list.status ⭐ | string | Current registration status of this GSTIN (e.g. Active, Inactive, Cancelled). |
| data.gstin_list.state ⭐ | string | Indian state or union territory where this GSTIN is registered. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "pan": "ABCDE1234F"
}
```

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "GSTIN fetch successful",
  "response_type_id": 1388,
  "data": {
    "pan": "ABCDE1234F",
    "gstin_list": [
      {
        "gstin": "29ABCDE1234F1Z5",
        "status": "Active",
        "state": "Maharashtra"
      },
      {
        "gstin": "27ABCDE1234F1Z2",
        "status": "Inactive",
        "state": "Karnataka"
      }
    ]
  }
}
```

## Error scenarios

| Status | Scenario |
| --- | --- |
| 200 | No GSTINs found for the given PAN |
| 400 | Invalid PAN format |
| 403 | Authentication failure — wrong or expired secret-key / timestamp |