Create Send Request

post

https://api.coingate.com/api/v2/send_requests

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Send Request Behavior with 2FA

With 2FA Enabled

Records are initially created in a draft state and require manual confirmation through the dashboard before processing can begin. Only after confirmation will requests be processed.

‘Send Request’ should be confirmed in the account dashboard under Payouts → Outgoing Payments

With 2FA Disabled

Requests are processed immediately upon creation, without requiring manual confirmation. You can enable or disable the 2FA setting at any time in the API section of the dashboard.

2FA Configuration

You can enable or disable the 2FA requirement for each ‘send request’ in API App → Select API App → 2FA Settings

API Response of Send Request

📘
Send Request Object
The Send Request response has the same structure as the Send Request Callback. For detailed descriptions of each field, please refer to the ‘Send Request Callback’ documentation page.

Form Data

ledger_account_id

string

required

Ledger account ID can be retrieved from https://api.coingate.com/api/v2/ledger/accounts

beneficiary_payout_setting_id

int32

required

Beneficiary payout setting ID can be retrieved from https://api.coingate.com/api/v2/beneficiaries

amount

string

required

Amount to send

amount_currency_id

int32

required

Currency of amount. Currency ID's can be seen on https://developer.coingate.com/reference/currencies

purpose

string

required

Purpose of sending

callback_url

string

Send an automated message to Merchant URL when request status is changed. For testing you can use requestcatcher.com tool. URL must be direct without redirection. Read about billing request callbacks here.

external_id

string

This field allows merchants to associate the record with their own internal reference. If provided, it must be unique.. (max length: 50)

Responses

Send Request Object

200200

422422