---
title: "Get Recipients API Reference"
description: "Retrieve the list of saved beneficiaries for a DMT sender."
canonical: "https://eps.eko.in/docs/dmt-get-recipients"
---


> **Canonical URL:** https://eps.eko.in/docs/dmt-get-recipients
> 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.

# Get Recipients API Reference

`GET https://staging.eko.in/ekoapi/v3/customer/payment/dmt-fino/sender/{customer_id}/recipients`

Retrieve the list of saved beneficiaries for a DMT sender.

Returns all beneficiaries (recipients) previously registered under the sender's DMT-Fino account. Use this before initiating a transfer — if the desired beneficiary already exists you can use their recipient_id directly to send money, skipping Add Recipient.

> View product & pricing details: [Domestic Money Transfer (DMT)](https://eps.eko.in/products/dmt-api.md)

## Path parameters

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| customer_id | string | yes | Sender's 10-digit mobile number. e.g. 9123456789 |

## Query 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 |

## 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.count | number | Total number of recipients registered under this sender. |
| data.recipient | array | List of registered beneficiaries. |
| data.recipient.recipient_id ⭐ | number | Unique identifier for the recipient. Used as input to Send OTP and Initiate Transfer APIs. |
| data.recipient.recipient_name ⭐ | string | Full name of the beneficiary. |
| data.recipient.account | string | Beneficiary's bank account number. |
| data.recipient.ifsc | string | IFSC code of the beneficiary's bank branch. |
| data.recipient.bank_name | string | Name of the beneficiary's bank. |
| data.recipient.recipient_mobile | string | Mobile number registered for the recipient. |
| data.recipient.is_verified | boolean | Whether the recipient's account has been penny-drop verified. |

## Example response

```json
{
  "status": 0,
  "response_status_id": 0,
  "message": "Success",
  "response_type_id": 1388,
  "data": {
    "count": 2,
    "recipient": [
      {
        "recipient_id": 98765,
        "recipient_name": "Sunil Sharma",
        "account": "012345678901",
        "ifsc": "SBIN0001234",
        "bank_name": "State Bank of India",
        "recipient_mobile": "9988776655",
        "is_verified": true
      },
      {
        "recipient_id": 98766,
        "recipient_name": "Priya Verma",
        "account": "987654321098",
        "ifsc": "HDFC0002345",
        "bank_name": "HDFC Bank",
        "recipient_mobile": "9811223344",
        "is_verified": true
      }
    ]
  }
}
```
