---
title: "Add Recipient API Reference"
description: "Register a new beneficiary under a PPI Levin sender's account."
canonical: "https://eps.eko.in/docs/ppi-levin-add-recipient"
---


> **Canonical URL:** https://eps.eko.in/docs/ppi-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/ppi-levin/sender/{customer_id}/recipient`

Register a new beneficiary under a PPI Levin sender's account.

Adds a beneficiary (bank account) to a PPI Levin sender. On success a `recipient_id` is returned — use it to send transaction OTP and initiate the transfer. Maximum 5 recipients per day.

> View product & pricing details: [PPI Wallet](https://eps.eko.in/products/ppi-api.md)

## Path parameters

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

## 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 |
| bank_id | integer | yes | Unique ID assigned to the beneficiary's bank. e.g. 12 |
| recipient_name | string | yes | Full name of the recipient. e.g. Aditya |
| recipient_mobile | string | yes | Recipient's 10-digit mobile number. e.g. 9775597777 |
| recipient_type | string | yes | Recipient type. Value will be 3. e.g. 3 |
| account | string | yes | Recipient's bank account number. e.g. 1234567890657 |
| ifsc | string | yes | IFSC code of the recipient's bank branch. e.g. KKBK0000878 |
| type | string | no | Recipient identifier type. Defaults to `ifsc`. e.g. ifsc |
| account_type | string | no | Account type. Defaults to 1. e.g. 1 |

## 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.recipient_id ⭐ | number | Unique recipient identifier — use to transact. |
| data.recipient_mobile | string | Recipient's mobile number (echoed back). |
| data.customer_id | string | Sender's mobile number (echoed back). |

## Example request

```json
{
  "initiator_id": "9962981729",
  "user_code": "20810200",
  "client_ref_id": "REQ-20260101-001",
  "bank_id": 12,
  "recipient_name": "Aditya",
  "recipient_mobile": "9775597777",
  "recipient_type": "3",
  "account": "1234567890657",
  "ifsc": "KKBK0000878",
  "type": "ifsc",
  "account_type": "1"
}
```

## Example response

```json
{
  "response_status_id": 0,
  "data": {
    "initiator_id": "6000000094",
    "recipient_mobile": "9775597777",
    "recipient_id_type": "",
    "customer_id": "9444444444",
    "pipes": {},
    "recipient_id": 10017740
  },
  "response_type_id": 43,
  "message": "Success!Please transact using Recipientid",
  "status": 0
}
```