---
title: "Add Recipient API Reference"
description: "Add a new beneficiary, or update an existing one, under a DMT-Levin sender."
canonical: "https://eps.eko.in/docs/dmt-levin-add-recipient"
---


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

# Add Recipient API Reference

`POST https://staging.eko.in/ekoapi/v3/customer/payment/dmt-levin/sender/{customer_id}/recipient`

Add a new beneficiary, or update an existing one, under a DMT-Levin sender.

> [!WARNING]
> The UAT / Sandbox environment is not available for this API — requests to `https://staging.eko.in/ekoapi/v3` return an error response. Test it in Production.

Adds a new recipient or updates an existing recipient for the sender. Provide the recipient's name, mobile, bank account, IFSC and Eko `bank_id` (resolve it from the IFSC with Get IFSC Details). On success a `recipient_id` is returned — use it to send money. A sender can add a maximum of 5 recipients in a day.

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

## 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 |
| user_code | string | yes | User code value of the retailer from whom the request is coming. e.g. 99080253 |
| bank_id | integer | yes | Eko's unique ID for the recipient's bank. Resolve it from the IFSC with Get IFSC Details. e.g. 6 |
| recipient_name | string | yes | Full name of the recipient. e.g. Rahul |
| recipient_mobile | string | yes | Recipient's valid 10-digit mobile number. e.g. 8888888888 |
| recipient_type | integer | yes | Recipient type. Value will be 3. e.g. 3 |
| account | string | no | Recipient's bank account number used for receiving funds. e.g. 1234567891023 |
| ifsc | string | no | IFSC code of the recipient's bank branch. e.g. HDFC0000583 |
| account_type | integer | yes | Account type. Defaults to 1. e.g. 1 |
| type | string | yes | Recipient identifier type. Defaults to `ifsc`. e.g. ifsc |

## 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.recipient_id ⭐ | number | Unique recipient identifier — use it to send money. |
| data.customer_id | string | Sender's mobile number (echoed back). |
| data.recipient_mobile | string | Recipient mobile number (echoed back). |
| data.initiator_id | string | Partner initiator ID (echoed back). |
| data.pipes | object | Available settlement pipes for the new recipient. |

## Response types

Branch on `response_type_id` to decide the next call:

| response_type_id | Meaning | Next step |
| --- | --- | --- |
| 43 | Recipient added — proceed to Send Transaction OTP | [dmt-levin-send-otp](https://eps.eko.in/docs/dmt-levin-send-otp.md) |

## Example request

```json
{
  "initiator_id": "9962981729",
  "client_ref_id": "2026010100123456789",
  "user_code": "99080253",
  "bank_id": 6,
  "recipient_name": "Rahul",
  "recipient_mobile": "8888888888",
  "recipient_type": 3,
  "account": "1234567891023",
  "ifsc": "HDFC0000583",
  "account_type": 1,
  "type": "ifsc"
}
```

## Example response

`response_type_id` `43` — Recipient added — proceed to Send Transaction OTP. Next step: [dmt-levin-send-otp](https://eps.eko.in/docs/dmt-levin-send-otp.md).

```json
{
  "response_status_id": 0,
  "data": {
    "bank_recipient_id": "",
    "initiator_id": "7384421232",
    "recipient_mobile": "8888888888",
    "recipient_id_type": "",
    "customer_id": "9999999999",
    "pipes": {},
    "recipient_id": 116456986
  },
  "response_type_id": 43,
  "message": "Success!Please transact using Recipientid",
  "status": 0
}
```