Asset Management

Endpoint

Futures Transfer for Sub-account (For Master Account) (USER_DATA)

Futures Transfer for Sub-account

POST

/sapi/v1/sub-account/futures/transfer

https://api.binance.com

Futures Transfer for Sub-account (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Futures Transfer for Sub-account (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Futures Transfer for Sub-account (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Futures Transfer for Sub-account (For Master Account) (USER_DATA) › Request Body

email

string · required

Example: 123@test.com

asset

string · required

The asset being transferred

Example: USDT

amount

number · float · required

The amount to be transferred

Example: 1.0

type

integer · int64 · required

1: transfer from subaccount's spot account to its USDT-margined futures account 2: transfer from subaccount's USDT-margined futures account to its spot account 3: transfer from subaccount's spot account to its COIN-margined futures account 4 from subaccount's COIN-margined futures account to its spot account

Example: 1

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Futures Transfer for Sub-account (For Master Account) (USER_DATA) › Responses

200

Futures Transfer for Sub-account

txnId

string

Example: 2966662589

Get Detail on Sub-account's Futures Account (For Master Account) (USER_DATA)

Get Detail on Sub-account's Futures Account

GET

/sapi/v1/sub-account/futures/account

https://api.binance.com

Get Detail on Sub-account's Futures Account (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Detail on Sub-account's Futures Account (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

Get Detail on Sub-account's Futures Account (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Detail on Sub-account's Futures Account (For Master Account) (USER_DATA) › Query Parameters

email

string · required

Example: 123@test.com

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Detail on Sub-account's Futures Account (For Master Account) (USER_DATA) › Responses

200

Get Detail on Sub-account's Futures Account

email

string

Example: abc@test.com

asset

string

Example: USDT

object[]

canDeposit

boolean

Example: true

canTrade

boolean

Example: true

canWithdraw

boolean

Example: true

feeTier

integer · int64

Example: 2

maxWithdrawAmount

string

Example: 0.88308000

totalInitialMargin

string

Example: 0.00000000

totalMaintenanceMargin

string

Example: 0.00000000

totalMarginBalance

string

Example: 0.88308000

totalOpenOrderInitialMargin

string

Example: 0.00000000

totalPositionInitialMargin

string

Example: 0.00000000

totalUnrealizedProfit

string

Example: 0.00000000

totalWalletBalance

string

Example: 0.88308000

updateTime

integer · int64

Example: 1576756674610

GET/sapi/v1/sub-account/futures/account

curl --request GET \
  --url 'https://api.binance.com/sapi/v1/sub-account/futures/account?email=%3Cstring%3E&timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

{
  "email": "abc@test.com",
  "asset": "USDT",
  "assets": [
    {
      "asset": "USDT",
      "initialMargin": "0.00000000",
      "maintenanceMargin": "0.00000000",
      "marginBalance": "0.88308000",
      "maxWithdrawAmount": "0.88308000",
      "openOrderInitialMargin": "0.00000000",
      "positionInitialMargin": "0.00000000",
      "unrealizedProfit": "0.00000000",
      "walletBalance": "0.88308000"
    }
  ],
  "canDeposit": true,
  "canTrade": true,
  "canWithdraw": true,
  "feeTier": 2,
  "maxWithdrawAmount": "0.88308000",
  "totalInitialMargin": "0.00000000",
  "totalMaintenanceMargin": "0.00000000",
  "totalMarginBalance": "0.88308000",
  "totalOpenOrderInitialMargin": "0.00000000",
  "totalPositionInitialMargin": "0.00000000",
  "totalUnrealizedProfit": "0.00000000",
  "totalWalletBalance": "0.88308000",
  "updateTime": 1576756674610
}

json

application/json

Get Detail on Sub-account's Futures Account V2 (For Master Account) (USER_DATA)

Get Detail on Sub-account's Futures Account

GET

/sapi/v2/sub-account/futures/account

https://api.binance.com

Get Detail on Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Detail on Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Get Detail on Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Detail on Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Query Parameters

email

string · required

Example: 123@test.com

futuresType

integer · int64 · required

1 Futures，2: Coin-margined Futures

Example: 1

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Detail on Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Responses

200

Get Detail on Sub-account's Futures Account V2

object

GET/sapi/v2/sub-account/futures/account

curl --request GET \
  --url 'https://api.binance.com/sapi/v2/sub-account/futures/account?email=%3Cstring%3E&futuresType=%3Cnumber%3E&timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

{
  "futureAccountResp": {
    "email": "abc@test.com",
    "assets": [
      {
        "asset": "USDT",
        "initialMargin": "0.00000000",
        "maintenanceMargin": "0.00000000",
        "marginBalance": "0.88308000",
        "maxWithdrawAmount": "0.88308000",
        "openOrderInitialMargin": "0.00000000",
        "positionInitialMargin": "0.00000000",
        "unrealizedProfit": "0.00000000",
        "walletBalance": "0.88308000"
      }
    ],
    "canDeposit": true,
    "canTrade": true,
    "canWithdraw": true,
    "feeTier": 2,
    "maxWithdrawAmount": "0.88308000",
    "totalInitialMargin": "0.00000000",
    "totalMaintenanceMargin": "0.00000000",
    "totalMarginBalance": "0.88308000",
    "totalOpenOrderInitialMargin": "0.00000000",
    "totalPositionInitialMargin": "0.00000000",
    "totalUnrealizedProfit": "0.00000000",
    "totalWalletBalance": "0.88308000",
    "updateTime": 1576756674610
  },
  "deliveryAccountResp": {
    "email": "abc@test.com",
    "assets": [
      {
        "asset": "BTC",
        "initialMargin": "0.00000000",
        "maintenanceMargin": "0.00000000",
        "marginBalance": "0.88308000",
        "maxWithdrawAmount": "0.88308000",
        "openOrderInitialMargin": "0.00000000",
        "positionInitialMargin": "0.00000000",
        "unrealizedProfit": "0.00000000",
        "walletBalance": "0.88308000"
      }
    ],
    "canDeposit": true,
    "canTrade": true,
    "canWithdraw": true,
    "feeTier": 2,
    "updateTime": 1598959682001
  }
}

json

application/json

Get Detail on Sub-account's Margin Account (For Master Account) (USER_DATA)

Get Detail on Sub-account's Margin Account

GET

/sapi/v1/sub-account/margin/account

https://api.binance.com

Get Detail on Sub-account's Margin Account (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Detail on Sub-account's Margin Account (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

Get Detail on Sub-account's Margin Account (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Detail on Sub-account's Margin Account (For Master Account) (USER_DATA) › Query Parameters

email

string · required

Example: 123@test.com

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Detail on Sub-account's Margin Account (For Master Account) (USER_DATA) › Responses

200

Get Detail on Sub-account's Margin Account

email

string

Example: 123@test.com

marginLevel

string

Example: 11.64405625

totalAssetOfBtc

string

Example: 6.82728457

totalLiabilityOfBtc

string

Example: 0.58633215

totalNetAssetOfBtc

string

Example: 6.24095242

object

object[]

Get Move Position History for Sub-account (For Master Account) (USER_DATA)

Query move position history

GET

/sapi/v1/sub-account/futures/move-position

https://api.binance.com

Get Move Position History for Sub-account (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Move Position History for Sub-account (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Get Move Position History for Sub-account (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Move Position History for Sub-account (For Master Account) (USER_DATA) › Query Parameters

symbol

string · required

Example: BTCUSDT

page

integer · int64 · required

Example: 1

rows

integer · int64 · required

Example: 1

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

startTime

integer · int64

Example: 1623319461670

endTime

integer · int64

Example: 1641782889000

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Move Position History for Sub-account (For Master Account) (USER_DATA) › Responses

200

Get Move Position History for Sub-account

total

integer · int64

Example: 3

object[]

Move Position for Sub-account (For Master Account) (USER_DATA)

Move position between sub-master, master-sub, or sub-sub accounts when necessary

POST

/sapi/v1/sub-account/futures/move-position

https://api.binance.com

Move Position for Sub-account (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Move Position for Sub-account (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Move Position for Sub-account (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Move Position for Sub-account (For Master Account) (USER_DATA) › Request Body

fromUserEmail

string · required

Example: testFrom@google.com

toUserEmail

string · required

Example: testTo@google.com

productType

string · enum · required

Enum values:

Example: UM

object[] · required

Max 10 positions supported. When input request parameter,orderArgs.symbol should be STRING, orderArgs.quantity should be BIGDECIMAL, and orderArgs.positionSide should be STRING, positionSide support BOTH,LONG and SHORT. Each entry should be like orderArgs[0].symbol=BTCUSDT,orderArgs[0].quantity=0.001,orderArgs[0].positionSide=BOTH. Example of the request parameter array: orderArgs[0].symbol=BTCUSDT orderArgs[0].quantity=0.001 orderArgs[0].positionSide=BOTH orderArgs[1].symbol=ETHUSDT orderArgs[1].quantity=0.01 orderArgs[1].positionSide=BOTH

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Move Position for Sub-account (For Master Account) (USER_DATA) › Responses

200

Move Position for Sub-account

object[]

POST/sapi/v1/sub-account/futures/move-position

curl --request POST \
  --url https://api.binance.com/sapi/v1/sub-account/futures/move-position \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data fromUserEmail=testFrom@google.com \
  --data toUserEmail=testTo@google.com \
  --data productType=UM \
  --data 'orderArgs={}' \
  --data timestamp=1770736694138

Example Request Body

{
  "fromUserEmail": "testFrom@google.com",
  "toUserEmail": "testTo@google.com",
  "productType": "UM",
  "orderArgs": [
    {}
  ],
  "timestamp": 1770736694138
}

json

Example Responses

{
  "movePositionOrders": [
    {
      "fromUserEmail": "testFrom@google.com",
      "toUserEmail": "testTo@google.com",
      "productType": "UM",
      "symbol": "BTCUSDT",
      "priceType": "MARK_PRICE",
      "price": "97139.00000000",
      "quantity": "0.001",
      "positionSide": "BOTH",
      "side": "BUY",
      "success": true
    }
  ]
}

json

application/json

Get Sub-account Deposit Address (For Master Account) (USER_DATA)

Fetch sub-account deposit address

GET

/sapi/v1/capital/deposit/subAddress

https://api.binance.com

Get Sub-account Deposit Address (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Sub-account Deposit Address (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Get Sub-account Deposit Address (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Sub-account Deposit Address (For Master Account) (USER_DATA) › Query Parameters

email

string · required

Example: 123@test.com

coin

string · required

Example: BTC

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

network

string

networks can be found in GET /sapi/v1/capital/deposit/address

Example: null

amount

number · float

Example: 1.0

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Sub-account Deposit Address (For Master Account) (USER_DATA) › Responses

200

Get Sub-account Deposit Address

address

string

Example: TDunhSa7jkTNuKrusUTU1MUHtqXoBPKETV

coin

string

Example: USDT

tag

string

Example:

url

string

Example: https://tronscan.org/#/address/TDunhSa7jkTNuKrusUTU1MUHtqXoBPKETV

Get Sub-account Deposit History (For Master Account) (USER_DATA)

Fetch sub-account deposit history

GET

/sapi/v1/capital/deposit/subHisrec

https://api.binance.com

Get Sub-account Deposit History (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Sub-account Deposit History (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Get Sub-account Deposit History (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Sub-account Deposit History (For Master Account) (USER_DATA) › Query Parameters

email

string · required

Example: 123@test.com

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

includeSource

boolean

Default false, return sourceAddress field when set to true

Example: false

Default: false

coin

string

Example: BTC

status

integer · int64

Deposit status: 0=pending, 6=credited but cannot withdraw, 7=wrong deposit, 8=waiting user confirmation, 1=success.

Example: 0

startTime

integer · int64

Example: 1623319461670

endTime

integer · int64

Example: 1641782889000

limit

integer · int64 · max: 200

Example: 1

Default: 1

offset

integer · int64

Example: 0

Default: 0

recvWindow

integer · int64 · max: 60000

Example: 5000

txId

string

Example: 1

Get Sub-account Deposit History (For Master Account) (USER_DATA) › Responses

200

Get Sub-account Deposit History

object

id

string

Example: 769800519366885376

amount

string

Example: 0.001

coin

string

Example: BNB

network

string

Example: BNB

status

integer · int64

Deposit status: 0=pending, 6=credited but cannot withdraw, 7=wrong deposit, 8=waiting user confirmation, 1=success.

Example: 0

address

string

Example: bnb136ns6lfw4zs5hg4n85vdthaad7hq5m4gtkgf23

addressTag

string

Example: 101764890

txId

string

Example: 98A3EA560C6B3336D348B6C83F0F95ECE4F1F5919E94BD006E5BF3BF264FACFC

insertTime

integer · int64

Example: 1661493146000

transferType

integer · int64

Example: 0

confirmTimes

string

Example: 1/1

unlockConfirm

integer · int64

Example: 0

walletType

integer · int64

Example: 0

Get Summary of Sub-account's Futures Account (For Master Account) (USER_DATA)

Get Summary of Sub-account's Futures Account

GET

/sapi/v1/sub-account/futures/accountSummary

https://api.binance.com

Get Summary of Sub-account's Futures Account (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Summary of Sub-account's Futures Account (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Get Summary of Sub-account's Futures Account (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Summary of Sub-account's Futures Account (For Master Account) (USER_DATA) › Query Parameters

page

integer · int64 · required

Example: 1

limit

integer · int64 · max: 500 · required

Example: 1

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Summary of Sub-account's Futures Account (For Master Account) (USER_DATA) › Responses

200

Get Summary of Sub-account's Futures Account

totalInitialMargin

string

Example: 9.83137400

totalMaintenanceMargin

string

Example: 0.41568700

totalMarginBalance

string

Example: 23.03235621

totalOpenOrderInitialMargin

string

Example: 9.00000000

totalPositionInitialMargin

string

Example: 0.83137400

totalUnrealizedProfit

string

Example: 0.03219710

totalWalletBalance

string

Example: 22.15879444

asset

string

Example: USD

object[]

GET/sapi/v1/sub-account/futures/accountSummary

curl --request GET \
  --url 'https://api.binance.com/sapi/v1/sub-account/futures/accountSummary?page=%3Cnumber%3E&limit=%3Cnumber%3E&timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

{
  "totalInitialMargin": "9.83137400",
  "totalMaintenanceMargin": "0.41568700",
  "totalMarginBalance": "23.03235621",
  "totalOpenOrderInitialMargin": "9.00000000",
  "totalPositionInitialMargin": "0.83137400",
  "totalUnrealizedProfit": "0.03219710",
  "totalWalletBalance": "22.15879444",
  "asset": "USD",
  "subAccountList": [
    {
      "email": "123@test.com",
      "totalInitialMargin": "9.00000000",
      "totalMaintenanceMargin": "0.00000000",
      "totalMarginBalance": "22.12659734",
      "totalOpenOrderInitialMargin": "9.00000000",
      "totalPositionInitialMargin": "0.00000000",
      "totalUnrealizedProfit": "0.00000000",
      "totalWalletBalance": "22.12659734",
      "asset": "USD"
    }
  ]
}

json

application/json

Get Summary of Sub-account's Futures Account V2 (For Master Account) (USER_DATA)

Get Summary of Sub-account's Futures Account

GET

/sapi/v2/sub-account/futures/accountSummary

https://api.binance.com

Get Summary of Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Summary of Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

Get Summary of Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Summary of Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Query Parameters

futuresType

integer · int64 · required

1 Futures，2: Coin-margined Futures

Example: 1

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

page

integer · int64

Example: 1

Default: 1

limit

integer · int64 · max: 20

Example: 10

Default: 10

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Summary of Sub-account's Futures Account V2 (For Master Account) (USER_DATA) › Responses

200

Get Summary of Sub-account's Futures Account V2

object

GET/sapi/v2/sub-account/futures/accountSummary

curl --request GET \
  --url 'https://api.binance.com/sapi/v2/sub-account/futures/accountSummary?futuresType=%3Cnumber%3E&timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

{
  "futureAccountSummaryResp": {
    "totalInitialMargin": "9.83137400",
    "totalMaintenanceMargin": "0.41568700",
    "totalMarginBalance": "23.03235621",
    "totalOpenOrderInitialMargin": "9.00000000",
    "totalPositionInitialMargin": "0.83137400",
    "totalUnrealizedProfit": "0.03219710",
    "totalWalletBalance": "22.15879444",
    "asset": "USD",
    "subAccountList": [
      {
        "email": "123@test.com",
        "totalInitialMargin": "9.00000000",
        "totalMaintenanceMargin": "0.00000000",
        "totalMarginBalance": "22.12659734",
        "totalOpenOrderInitialMargin": "9.00000000",
        "totalPositionInitialMargin": "0.00000000",
        "totalUnrealizedProfit": "0.00000000",
        "totalWalletBalance": "22.12659734",
        "asset": "USD"
      }
    ]
  },
  "deliveryAccountSummaryResp": {
    "totalMarginBalanceOfBTC": "25.03221121",
    "totalUnrealizedProfitOfBTC": "0.12233410",
    "totalWalletBalanceOfBTC": "22.15879444",
    "asset": "BTC",
    "subAccountList": [
      {
        "email": "123@test.com",
        "totalMarginBalance": "22.12659734",
        "totalUnrealizedProfit": "0.00000000",
        "totalWalletBalance": "22.12659734",
        "asset": "BTC"
      }
    ]
  }
}

json

application/json

Get Summary of Sub-account's Margin Account (For Master Account) (USER_DATA)

Get Summary of Sub-account's Margin Account

GET

/sapi/v1/sub-account/margin/accountSummary

https://api.binance.com

Get Summary of Sub-account's Margin Account (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Get Summary of Sub-account's Margin Account (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

Get Summary of Sub-account's Margin Account (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Get Summary of Sub-account's Margin Account (For Master Account) (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Summary of Sub-account's Margin Account (For Master Account) (USER_DATA) › Responses

200

Get Summary of Sub-account's Margin Account

totalAssetOfBtc

string

Example: 4.33333333

totalLiabilityOfBtc

string

Example: 2.11111112

totalNetAssetOfBtc

string

Example: 2.22222221

object[]

Margin Transfer for Sub-account (For Master Account) (USER_DATA)

Margin Transfer for Sub-account

POST

/sapi/v1/sub-account/margin/transfer

https://api.binance.com

Margin Transfer for Sub-account (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Margin Transfer for Sub-account (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Margin Transfer for Sub-account (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Margin Transfer for Sub-account (For Master Account) (USER_DATA) › Request Body

email

string · required

Example: 123@test.com

asset

string · required

The asset being transferred

Example: BTC

amount

number · float · required

The amount to be transferred

Example: 1.0

type

integer · int64 · required

1: transfer from subaccount's spot account to margin account 2: transfer from subaccount's margin account to its spot account

Example: 1

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Margin Transfer for Sub-account (For Master Account) (USER_DATA) › Responses

200

Margin Transfer for Sub-account

txnId

string

Example: 2966662589

Query Sub-account Assets (For Master Account) (USER_DATA)

Fetch sub-account assets

GET

/sapi/v3/sub-account/assets

https://api.binance.com

Query Sub-account Assets (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Query Sub-account Assets (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight60

Query Sub-account Assets (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Query Sub-account Assets (For Master Account) (USER_DATA) › Query Parameters

email

string · required

Example: 123@test.com

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Query Sub-account Assets (For Master Account) (USER_DATA) › Responses

200

Sub-account Assets

object[]

Query Sub-account Assets V4 (For Master Account) (USER_DATA)

Fetch sub-account assets

GET

/sapi/v4/sub-account/assets

https://api.binance.com

Query Sub-account Assets V4 (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Query Sub-account Assets V4 (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight60

Query Sub-account Assets V4 (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Query Sub-account Assets V4 (For Master Account) (USER_DATA) › Query Parameters

email

string · required

Example: 123@test.com

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Query Sub-account Assets V4 (For Master Account) (USER_DATA) › Responses

200

Sub-account Assets

object[]

Query Sub-account Futures Asset Transfer History (For Master Account) (USER_DATA)

Query Sub-account Futures Asset Transfer History

GET

/sapi/v1/sub-account/futures/internalTransfer

https://api.binance.com

Query Sub-account Futures Asset Transfer History (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Query Sub-account Futures Asset Transfer History (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Query Sub-account Futures Asset Transfer History (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Query Sub-account Futures Asset Transfer History (For Master Account) (USER_DATA) › Query Parameters

email

string · required

Example: 123@test.com

futuresType

integer · int64 · required

1 Futures，2: Coin-margined Futures

Example: 1

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

startTime

integer · int64

Cannot be earlier than 1 month ago

Example: 1623319461670

endTime

integer · int64

Example: 1641782889000

page

integer · int64

Example: 1

Default: 1

limit

integer · int64 · max: 500

Example: 10

Default: 50

recvWindow

integer · int64 · max: 60000

Example: 5000

Query Sub-account Futures Asset Transfer History (For Master Account) (USER_DATA) › Responses

200

Sub-account Futures Asset Transfer History

success

boolean

Example: true

futuresType

integer · int64

Example: 2

object[]

Sub-account Futures Asset Transfer (For Master Account) (USER_DATA)

Sub-account Futures Asset Transfer

POST

/sapi/v1/sub-account/futures/internalTransfer

https://api.binance.com

Sub-account Futures Asset Transfer (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Sub-account Futures Asset Transfer (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Sub-account Futures Asset Transfer (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Sub-account Futures Asset Transfer (For Master Account) (USER_DATA) › Request Body

fromEmail

string · required

Sender email

Example: abc@test.com

toEmail

string · required

Recipient email

Example: def@test.com

futuresType

integer · int64 · required

1 Futures，2: Coin-margined Futures

Example: 1

asset

string · required

Example: BTC

amount

number · float · required

Example: 1.0

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Sub-account Futures Asset Transfer (For Master Account) (USER_DATA) › Responses

200

Sub-account Futures Asset Transfer

success

boolean

Example: true

txnId

string

Example: 2934662589

Query Sub-account Spot Assets Summary (For Master Account) (USER_DATA)

Get BTC valued asset summary of subaccounts.

GET

/sapi/v1/sub-account/spotSummary

https://api.binance.com

Query Sub-account Spot Assets Summary (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Query Sub-account Spot Assets Summary (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Query Sub-account Spot Assets Summary (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Query Sub-account Spot Assets Summary (For Master Account) (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

email

string

Managed sub-account email

Example: 123@test.com

page

integer · int64

Example: 1

Default: 1

size

integer · int64 · max: 20

Example: 10

Default: 10

recvWindow

integer · int64 · max: 60000

Example: 5000

Query Sub-account Spot Assets Summary (For Master Account) (USER_DATA) › Responses

200

Sub-account Spot Assets Summary

totalCount

integer · int64

Example: 2

masterAccountTotalAsset

string

Example: 0.23231201

object[]

Query Sub-account Spot Asset Transfer History (For Master Account) (USER_DATA)

Query Sub-account Spot Asset Transfer History

GET

/sapi/v1/sub-account/sub/transfer/history

https://api.binance.com

Query Sub-account Spot Asset Transfer History (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Query Sub-account Spot Asset Transfer History (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Query Sub-account Spot Asset Transfer History (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Query Sub-account Spot Asset Transfer History (For Master Account) (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

fromEmail

string

Example: aaa@test.com

toEmail

string

Example: bbb@test.com

startTime

integer · int64

Example: 1623319461670

endTime

integer · int64

Example: 1641782889000

page

integer · int64

Example: 1

Default: 1

limit

integer · int64 · max: 200

Example: 10

Default: 500

recvWindow

integer · int64 · max: 60000

Example: 5000

Query Sub-account Spot Asset Transfer History (For Master Account) (USER_DATA) › Responses

200

Sub-account Spot Asset Transfer History

object

from

string

Example: aaa@test.com

to

string

Example: bbb@test.com

asset

string

Example: BTC

qty

string

Example: 10

status

string

Example: SUCCESS

tranId

integer · int64

Example: 6489943656

time

integer · int64

Example: 1544433328000

Query Universal Transfer History (For Master Account) (USER_DATA)

Query Universal Transfer History

GET

/sapi/v1/sub-account/universalTransfer

https://api.binance.com

Query Universal Transfer History (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Query Universal Transfer History (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Query Universal Transfer History (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Query Universal Transfer History (For Master Account) (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

fromEmail

string

Example: abctest@gmail.com

toEmail

string

Example: deftest@gmail.com

clientTranId

string

Example: 1

startTime

integer · int64

Example: 1623319461670

endTime

integer · int64

Example: 1641782889000

page

integer · int64

Example: 1

Default: 1

limit

integer · int64 · max: 500

Example: 10

Default: 500

recvWindow

integer · int64 · max: 60000

Example: 5000

Query Universal Transfer History (For Master Account) (USER_DATA) › Responses

200

Universal Transfer History

object[]

totalCount

integer · int64

Example: 1

Universal Transfer (For Master Account) (USER_DATA)

Universal Transfer

POST

/sapi/v1/sub-account/universalTransfer

https://api.binance.com

Universal Transfer (For Master Account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Universal Transfer (For Master Account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight360

Universal Transfer (For Master Account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Universal Transfer (For Master Account) (USER_DATA) › Request Body

fromAccountType

string · enum · required

Enum values:

SPOT

USDT_FUTURE

COIN_FUTURE

MARGIN

ISOLATED_MARGIN

Example: SPOT

toAccountType

string · enum · required

Enum values:

SPOT

USDT_FUTURE

COIN_FUTURE

MARGIN

ISOLATED_MARGIN

Example: SPOT

asset

string · required

Example: BTC

amount

number · float · required

Example: 1.0

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

fromEmail

string

Example: abc@test.com

toEmail

string

Example: def@test.com

clientTranId

string

Must be unique

Example: 1

symbol

string

Only supported under ISOLATED_MARGIN type

Example: BTCUSDT

recvWindow

integer · int64 · max: 60000

Example: 5000

Universal Transfer (For Master Account) (USER_DATA) › Responses

200

Universal Transfer

tranId

integer · int64

Example: 11945860693

clientTranId

string

Example: test

Sub-account Transfer History (For Sub-account) (USER_DATA)

Sub-account Transfer History

GET

/sapi/v1/sub-account/transfer/subUserHistory

https://api.binance.com

Sub-account Transfer History (For Sub-account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Sub-account Transfer History (For Sub-account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Sub-account Transfer History (For Sub-account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Sub-account Transfer History (For Sub-account) (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

asset

string

If not sent, result of all assets will be returned

Example: BTC

type

integer · int64

1: transfer in, 2: transfer out

Example: 1

startTime

integer · int64

Example: 1623319461670

endTime

integer · int64

Example: 1641782889000

limit

integer · int64 · max: 200

Example: 10

Default: 500

returnFailHistory

boolean

Default False, return PROCESS and SUCCESS status history; If True,return PROCESS and SUCCESS and FAILURE status history

Example: false

Default: false

recvWindow

integer · int64 · max: 60000

Example: 5000

Sub-account Transfer History (For Sub-account) (USER_DATA) › Responses

200

Sub-account Transfer History

object

counterParty

string

Example: master

email

string

Example: master@test.com

type

integer · int64

Example: 1

asset

string

Example: BTC

qty

string

Example: 1

fromAccountType

string

Example: SPOT

toAccountType

string

Example: SPOT

status

string

Example: SUCCESS

tranId

integer · int64

Example: 11798835829

time

integer · int64

Example: 1544433325000

Transfer to Master (For Sub-account) (USER_DATA)

Transfer to Master

POST

/sapi/v1/sub-account/transfer/subToMaster

https://api.binance.com

Transfer to Master (For Sub-account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Transfer to Master (For Sub-account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Transfer to Master (For Sub-account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Transfer to Master (For Sub-account) (USER_DATA) › Request Body

asset

string · required

Example: BTC

amount

number · float · required

Example: 1.0

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Transfer to Master (For Sub-account) (USER_DATA) › Responses

200

Transfer to Master

txnId

string

Example: 2966662589

Transfer to Sub-account of Same Master (For Sub-account) (USER_DATA)

Transfer to Sub-account of Same Master

POST

/sapi/v1/sub-account/transfer/subToSub

https://api.binance.com

Transfer to Sub-account of Same Master (For Sub-account) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Transfer to Sub-account of Same Master (For Sub-account) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Transfer to Sub-account of Same Master (For Sub-account) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Transfer to Sub-account of Same Master (For Sub-account) (USER_DATA) › Request Body

toEmail

string · required

Example: abc@test.com

asset

string · required

Example: BTC

amount

number · float · required

Example: 1.0

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

Transfer to Sub-account of Same Master (For Sub-account) (USER_DATA) › Responses

200

Transfer to Sub-account of Same Master

txnId

string

Example: 2966662589