Skip to main content
POST
Create Sub-Account
The email field requirement depends on the shareKyc parameter:
  • When shareKyc is false or not provided: email is required
  • When shareKyc is true: email is optional

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
alias
string
required

Name for sub-account

Example:

"trading_bot"

permissions
object
required
email
string

Sub-account email (required when shareKyc is false)

Example:

"sub@example.com"

shareKyc
boolean

If KYC shared with main account

Example:

false

Response

Sub-account created successfully

id
string

Sub-account identifier

Example:

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

alias
string

Sub-account alias/name

Example:

"trading_bot"

userId
string

User identifier associated with account

Example:

"u-12345"

email
string

Sub-account email (masked)

Example:

"s***@example.com"

status
string

Sub-account status

Example:

"active"

color
string

Sub-account color

Example:

"#FF5733"

kyc
object

KYC information

permissions
object

Sub-account permissions