Skip to main content
Sub-Account Transfer

Used in these guides

Authorizations

X-TXC-APIKEY
string
header
required

The public WhiteBIT API key.

X-TXC-PAYLOAD
string
header
required

Base64-encoded JSON request body.

X-TXC-SIGNATURE
string
header
required

HMAC-SHA512 signature of the payload, hex-encoded. Computed as hex(HMAC-SHA512(payload, api_secret)).

Body

application/json
id
string
required

Sub-account id

Example:

"8e667b4a-0b71-4988-8af5-9474dbfaeb51"

direction
enum<string>
required

Transfer direction

Available options:
main_to_sub,
sub_to_main
Example:

"main_to_sub"

amount
string
required

Transfer amount (min 0.00000001)

Example:

"0.5"

ticker
string
required

Currency's ticker

Example:

"ETH"

Response

Transfer request accepted. The transfer can still fail after the response, so confirm it on the sub-account's main balance with Sub-Account Balances.

transaction_id
string

External identifier of the transfer request. The same value identifies the request's record in Get Sub-Account Transfer History. That record does not confirm that the funds moved.