Account Management

Endpoint

Create a Virtual Sub-account (For Master Account) (USER_DATA)

Create a Virtual Sub-account

POST

/sapi/v1/sub-account/virtualSubAccount

https://api.binance.com

Create a Virtual 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

Create a Virtual 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

Create a Virtual 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

Create a Virtual Sub-account (For Master Account) (USER_DATA) › Request Body

subAccountString

string · required

Please input a string. We will create a virtual email using that string for you to register

Example: testSubAccount

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

Create a Virtual Sub-account (For Master Account) (USER_DATA) › Responses

200

Create a Virtual Sub-account

email

string

Example: addsdd_virtual@aasaixwqnoemail.com

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

Enable Futures for Sub-account for Master Account

POST

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

https://api.binance.com

Enable Futures 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

Enable Futures 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

Enable Futures 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

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

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

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

200

Enable Futures for Sub-account

email

string

Example: 123@test.com

isFuturesEnabled

boolean

Example: true

Enable Options for Sub-account (For Master Account) (USER_DATA)

Enable Options for Sub-account (For Master Account).

POST

/sapi/v1/sub-account/eoptions/enable

https://api.binance.com

Enable Options 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

Enable Options 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

Enable Options 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

Enable Options for Sub-account (For Master Account) (USER_DATA) › Request Body

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

Enable Options for Sub-account (For Master Account) (USER_DATA) › Responses

200

Enable Options for Sub-account

email

string

Example: 123@test.com

isEOptionsEnabled

boolean

Example: true

Get Futures Position-Risk of Sub-account (For Master Account) (USER_DATA)

Get Futures Position-Risk of Sub-account

GET

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

https://api.binance.com

Get Futures Position-Risk of 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 Futures Position-Risk of 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 Weight10

Get Futures Position-Risk of 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 Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-account (For Master Account) (USER_DATA) › Responses

200

Get Futures Position-Risk of Sub-account

object

entryPrice

string

Example: 9975.12000

leverage

string

Example: 50

maxNotional

string

Example: 1000000

liquidationPrice

string

Example: 7963.54

markPrice

string

Example: 9973.50770517

positionAmount

string

Example: 0.010

symbol

string

Example: BTCUSDT

unrealizedProfit

string

Example: -0.01612295

Get Futures Position-Risk of Sub-account V2 (For Master Account) (USER_DATA)

Get Futures Position-Risk of Sub-account V2

GET

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

https://api.binance.com

Get Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-account V2 (For Master Account) (USER_DATA) › Responses

200

Get Futures Position-Risk of Sub-account V2

object[]

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

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

Example Responses

{
  "futurePositionRiskVos": [
    {
      "entryPrice": "9975.12000",
      "leverage": "50",
      "maxNotional": "1000000",
      "liquidationPrice": "7963.54",
      "markPrice": "9973.50770517",
      "positionAmount": "0.010",
      "symbol": "BTCUSDT",
      "unrealizedProfit": "-0.01612295"
    }
  ],
  "deliveryPositionRiskVos": [
    {
      "entryPrice": "9975.12000",
      "markPrice": "9973.50770517",
      "leverage": "20",
      "isolated": "false",
      "isolatedWallet": "9973.50770517",
      "isolatedMargin": "0.00000000",
      "isAutoAddMargin": "false",
      "positionSide": "BOTH",
      "positionAmount": "1.230",
      "symbol": "BTCUSD_201225",
      "unrealizedProfit": "-0.01612295"
    }
  ]
}

json

application/json

Get Sub-account's Status on Margin Or Futures (For Master Account) (USER_DATA)

Get Sub-account's Status on Margin Or Futures

GET

/sapi/v1/sub-account/status

https://api.binance.com

Get Sub-account's Status on Margin Or Futures (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's Status on Margin Or Futures (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 Sub-account's Status on Margin Or Futures (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's Status on Margin Or Futures (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

Example: 123@test.com

recvWindow

integer · int64 · max: 60000

Example: 5000

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

200

Get Sub-account's Status on Margin Or Futures

object

email

string

Example: 123@test.com

isSubUserEnabled

boolean

Example: true

isUserActive

boolean

Example: true

insertTime

integer · int64

Example: 1570791523523

isMarginEnabled

boolean

Example: true

isFutureEnabled

boolean

Example: true

mobile

integer · int64

Example: 1570791523523

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

Query Sub-account List

GET

/sapi/v1/sub-account/list

https://api.binance.com

Query Sub-account List (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 List (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 List (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 List (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

Example: 123@test.com

isFreeze

string

Example: true

page

integer · int64

Example: 1

Default: 1

limit

integer · int64 · max: 200

Example: 10

Default: 1

recvWindow

integer · int64 · max: 60000

Example: 5000

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

200

Sub-account List

object[]

Query Sub-account Transaction Statistics (For Master Account) (USER_DATA)

Query Sub-account Transaction statistics (For Master Account).

GET

/sapi/v1/sub-account/transaction-statistics

https://api.binance.com

Query Sub-account Transaction Statistics (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 Transaction Statistics (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 Weight60

Query Sub-account Transaction Statistics (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 Transaction Statistics (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: abc@test.com

recvWindow

integer · int64 · max: 60000

Example: 5000

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

200

Sub-account Transaction Statistics

recent30BtcTotal

string

Example: 0

recent30BtcFuturesTotal

string

Example: 0

recent30BtcMarginTotal

string

Example: 0

recent30BusdTotal

string

Example: 0

recent30BusdFuturesTotal

string

Example: 0

recent30BusdMarginTotal

string

Example: 0

object[]

Account Management

Endpoint

Download schema

Create a Virtual Sub-account (For Master Account) (USER_DATA)

Create a Virtual Sub-account

POST

/sapi/v1/sub-account/virtualSubAccount

https://api.binance.com

Create a Virtual 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

Create a Virtual 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

Create a Virtual 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

Create a Virtual Sub-account (For Master Account) (USER_DATA) › Request Body

subAccountString

string · required

Please input a string. We will create a virtual email using that string for you to register

Example: testSubAccount

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

Create a Virtual Sub-account (For Master Account) (USER_DATA) › Responses

200

Create a Virtual Sub-account

email

string

Example: addsdd_virtual@aasaixwqnoemail.com

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

Enable Futures for Sub-account for Master Account

POST

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

https://api.binance.com

Enable Futures 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

Enable Futures 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

Enable Futures 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

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

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

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

200

Enable Futures for Sub-account

email

string

Example: 123@test.com

isFuturesEnabled

boolean

Example: true

Enable Options for Sub-account (For Master Account) (USER_DATA)

Enable Options for Sub-account (For Master Account).

POST

/sapi/v1/sub-account/eoptions/enable

https://api.binance.com

Enable Options 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

Enable Options 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

Enable Options 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

Enable Options for Sub-account (For Master Account) (USER_DATA) › Request Body

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

Enable Options for Sub-account (For Master Account) (USER_DATA) › Responses

200

Enable Options for Sub-account

email

string

Example: 123@test.com

isEOptionsEnabled

boolean

Example: true

Get Futures Position-Risk of Sub-account (For Master Account) (USER_DATA)

Get Futures Position-Risk of Sub-account

GET

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

https://api.binance.com

Get Futures Position-Risk of 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 Futures Position-Risk of 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 Weight10

Get Futures Position-Risk of 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 Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-account (For Master Account) (USER_DATA) › Responses

200

Get Futures Position-Risk of Sub-account

object

entryPrice

string

Example: 9975.12000

leverage

string

Example: 50

maxNotional

string

Example: 1000000

liquidationPrice

string

Example: 7963.54

markPrice

string

Example: 9973.50770517

positionAmount

string

Example: 0.010

symbol

string

Example: BTCUSDT

unrealizedProfit

string

Example: -0.01612295

Get Futures Position-Risk of Sub-account V2 (For Master Account) (USER_DATA)

Get Futures Position-Risk of Sub-account V2

GET

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

https://api.binance.com

Get Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-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 Futures Position-Risk of Sub-account V2 (For Master Account) (USER_DATA) › Responses

200

Get Futures Position-Risk of Sub-account V2

object[]

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

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

Example Responses

{
  "futurePositionRiskVos": [
    {
      "entryPrice": "9975.12000",
      "leverage": "50",
      "maxNotional": "1000000",
      "liquidationPrice": "7963.54",
      "markPrice": "9973.50770517",
      "positionAmount": "0.010",
      "symbol": "BTCUSDT",
      "unrealizedProfit": "-0.01612295"
    }
  ],
  "deliveryPositionRiskVos": [
    {
      "entryPrice": "9975.12000",
      "markPrice": "9973.50770517",
      "leverage": "20",
      "isolated": "false",
      "isolatedWallet": "9973.50770517",
      "isolatedMargin": "0.00000000",
      "isAutoAddMargin": "false",
      "positionSide": "BOTH",
      "positionAmount": "1.230",
      "symbol": "BTCUSD_201225",
      "unrealizedProfit": "-0.01612295"
    }
  ]
}

json

application/json

Get Sub-account's Status on Margin Or Futures (For Master Account) (USER_DATA)

Get Sub-account's Status on Margin Or Futures

GET

/sapi/v1/sub-account/status

https://api.binance.com

Get Sub-account's Status on Margin Or Futures (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's Status on Margin Or Futures (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 Sub-account's Status on Margin Or Futures (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's Status on Margin Or Futures (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

Example: 123@test.com

recvWindow

integer · int64 · max: 60000

Example: 5000

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

200

Get Sub-account's Status on Margin Or Futures

object

email

string

Example: 123@test.com

isSubUserEnabled

boolean

Example: true

isUserActive

boolean

Example: true

insertTime

integer · int64

Example: 1570791523523

isMarginEnabled

boolean

Example: true

isFutureEnabled

boolean

Example: true

mobile

integer · int64

Example: 1570791523523

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

Query Sub-account List

GET

/sapi/v1/sub-account/list

https://api.binance.com

Query Sub-account List (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 List (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 List (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 List (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

Example: 123@test.com

isFreeze

string

Example: true

page

integer · int64

Example: 1

Default: 1

limit

integer · int64 · max: 200

Example: 10

Default: 1

recvWindow

integer · int64 · max: 60000

Example: 5000

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

200

Sub-account List

object[]

Query Sub-account Transaction Statistics (For Master Account) (USER_DATA)

Query Sub-account Transaction statistics (For Master Account).

GET

/sapi/v1/sub-account/transaction-statistics

https://api.binance.com

Query Sub-account Transaction Statistics (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 Transaction Statistics (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 Weight60

Query Sub-account Transaction Statistics (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 Transaction Statistics (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: abc@test.com

recvWindow

integer · int64 · max: 60000

Example: 5000

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

200

Sub-account Transaction Statistics

recent30BtcTotal

string

Example: 0

recent30BtcFuturesTotal

string

Example: 0

recent30BtcMarginTotal

string

Example: 0

recent30BusdTotal

string

Example: 0

recent30BusdFuturesTotal

string

Example: 0

recent30BusdMarginTotal

string

Example: 0

object[]