---
title: "Bulk Bank Account Verification API Reference"
description: "Submit multiple bank accounts for penny-drop verification in a single API call; poll a status API for per-account results."
canonical: "https://eps.eko.in/docs/bulk-bank-account-verification"
---


> **Canonical URL:** https://eps.eko.in/docs/bulk-bank-account-verification
> 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 Bank Account Verification API Reference

`POST https://staging.eko.in/ekoapi/v3/tools/kyc/bank-account/bulk`

Submit multiple bank accounts for penny-drop verification in a single API call; poll a status API for per-account results.

**Behaviour**

- **Moves money**: Moves real money and cannot be undone. After a timeout, confirm the outcome before ever re-sending.
- **[₹2.04 + GST / verification](https://eps.eko.in/pricing?apis=bank-bulk#calculator)**: Billed per item inside the batch, not per call.

Accepts an array of bank account + IFSC pairs and enqueues them for asynchronous penny-drop verification. Returns a bulk_reference_id immediately; use the Bulk Bank Account Verification Status API to retrieve per-account results once processing completes. Ideal for batch onboarding, payroll runs, and large-scale disbursement pipelines where sequential single-account calls would be too slow.

> View product & pricing details: [Bank Account Verification](https://eps.eko.in/products/bank-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 (10–20 characters; 10 recommended). The SDKs generate one for every non-GET call when you don't. e.g. 2026010100123456789 |
| entries | array | yes | Array of bank account objects to verify. Each entry must contain a unique reference_id, bank_account and ifsc. e.g. [object Object],[object Object] |
| entries[].reference_id | string | yes | Your unique id for this entry within the batch. It is returned with this entry's result in the Bulk Bank Account Verification Status API. e.g. 1 |
| entries[].bank_account | string | yes | Bank account number for this entry. Send as a string to preserve leading zeros. e.g. 026291800001191 |
| entries[].ifsc | string | yes | IFSC code for this entry's bank account. e.g. YESB0000262 |

## 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 | UI display hint only (-1/0 success, 1 failure, 2 initiated, 3 refund initiated, 4 refunded). Never branch on it — use `status` (and `tx_status` for financial APIs), or `response_type_id` where documented. |
| 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.bulk_reference_id ⭐ | number | Unique reference ID for this bulk verification batch. Pass this to the Bulk Bank Account Verification Status API to poll for per-account results. |
| data.status ⭐ | string | Processing state of the batch (e.g. RECEIVED). |
| data.bulk_verification_id | string | Verification id assigned to the batch. |
| data.tid | number | Eko transaction id for this batch. Persist it for reconciliation. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "entries": [
    {
      "reference_id": "1",
      "bank_account": "026291800001191",
      "ifsc": "YESB0000262"
    },
    {
      "reference_id": "2",
      "bank_account": "00011020001772",
      "ifsc": "HDFC0000001"
    }
  ],
  "entries[].reference_id": "1",
  "entries[].bank_account": "026291800001191",
  "entries[].ifsc": "YESB0000262"
}
```

## Example response

```json
{
  "response_status_id": 0,
  "data": {
    "bulk_reference_id": 90438,
    "bulk_verification_id": "2887347146",
    "tid": 2887347146,
    "status": "RECEIVED"
  },
  "response_type_id": 0,
  "status": 0
}
```

## Error scenarios

| Status | response_type_id | Scenario |
| --- | --- | --- |
| 400 | `1` | Invalid or malformed entries array — missing required fields in one or more entries |
| 200 | `0` | Invalid IFSC in one or more entries — batch accepted but affected entries fail in status poll |