POSTSend Transaction OTP
Request an OTP to the sender's mobile number to authorise an upcoming DMT-Levin transfer.
https://staging.eko.in/ekoapi/v3 return an error response. Test it in Production.Generates an OTP and delivers it to the sender's registered mobile number as a pre-authorisation step before the money transfer. Provide the recipient_id, the transfer amount, and the sender's customer_id. The returned otp_ref_id must be passed to the transfer call along with the OTP entered by the customer.
Request
Body parameters
| Field | Type | Required | Description |
|---|---|---|---|
initiator_id | string | required | Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729 |
client_ref_id | string | optional | 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 | required | User code value of the retailer from whom the request is coming.e.g. 99080253 |
recipient_id | integer | required | Unique recipient ID returned by Add Recipient or Get Recipients.e.g. 116456986 |
amount | integer | required | Transfer amount in INR.e.g. 500 |
customer_id | string | required | Sender's 10-digit mobile number.e.g. 9999999999 |
beneficiary_id | string | optional | Unique ID generated when adding the recipient's bank details (see Get Recipients).e.g. 40378 |
initiator_idstringRequiredRegistered mobile number of the API user (see Platform Credentials).
example: 9962981729
client_ref_idstringoptionalUnique 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.
example: 2026010100123456789
user_codestringRequiredUser code value of the retailer from whom the request is coming.
example: 99080253
recipient_idintegerRequiredUnique recipient ID returned by Add Recipient or Get Recipients.
example: 116456986
amountintegerRequiredTransfer amount in INR.
example: 500
customer_idstringRequiredSender's 10-digit mobile number.
example: 9999999999
beneficiary_idstringoptionalUnique ID generated when adding the recipient's bank details (see Get Recipients).
example: 40378
These headers authenticate and sign every request. See How Auth Works for details.
| Field | Type | Required | Description |
|---|---|---|---|
developer_key | string | required | Static API key issued to your account after KYC. |
secret-key | string | required | Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))). |
secret-key-timestamp | string | required | Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time. |
content-type | string | required | application/jsone.g. application/json |
developer_keystringRequiredStatic API key issued to your account after KYC.
secret-keystringRequiredDynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
secret-key-timestampstringRequiredCurrent time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
content-typestringRequiredapplication/json
example: application/json
Response types
| response_type_id | Meaning | Next step |
|---|---|---|
2133 | Transaction OTP sent — proceed to Initiate Transaction | Initiate DMT-Levin Transaction |
Responses
2133Transaction OTP sent — proceed to Initiate TransactionNext:Initiate DMT-Levin Transaction
statusnumberPrimary success indicator (0 = success).
messagestringHuman-readable response / error message.
response_status_idnumberUI 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_idnumberA unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobjectAPI-specific response payload.
otp_ref_idstringReference ID for the OTP sent. Pass it to the transfer call along with the customer-entered OTP.