---
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.

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. e.g. REQ-20260101-001 |
| entries | array | yes | Array of bank account objects to verify. Each entry must contain bank_account and ifsc. Optionally include user_code per entry to attribute verifications to different retailers. e.g. [object Object],[object Object] |
| entries[].bank_account | string | yes | Bank account number for this entry. e.g. 1234567890 |
| entries[].ifsc | string | yes | IFSC code for this entry's bank account. e.g. SBIN0001234 |
| entries[].user_code | string | no | Per-entry retailer user code, if attributing individual verifications to different agents. e.g. 20810200 |

## 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.bulk_reference_id ⭐ | string | 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.reference_id | number | Numeric reference ID for the submitted batch request, used for internal tracking. |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "REQ-20260101-001",
  "entries": [
    {
      "bank_account": "1234567890",
      "ifsc": "SBIN0001234"
    },
    {
      "bank_account": "9876543210123",
      "ifsc": "HDFC0005678"
    }
  ],
  "entries[].bank_account": "1234567890",
  "entries[].ifsc": "SBIN0001234",
  "entries[].user_code": "20810200"
}
```

## Example response

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

## Error scenarios

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