Account

Endpoint

Account Information (USER_DATA)

Get current account information.

GET

/dapi/v1/account

https://dapi.binance.com

Account Information (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

Account Information (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 Weight5

Account Information (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

Account Information (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

Account Information (USER_DATA) › Responses

200

Account Information

object[]

Supported assets.

asset

string

asset name

Example: BTC

walletBalance

string

total wallet balance

Example: 0.00241969

unrealizedProfit

string

unrealized profit or loss

Example: 0.00000000

marginBalance

string

margin balance

Example: 0.00241969

maintMargin

string

maintenance margin

Example: 0.00000000

initialMargin

string

total intial margin required with the latest mark price

Example: 0.00000000

positionInitialMargin

string

positions" margin required with the latest mark price

Example: 0.00000000

openOrderInitialMargin

string

open orders" intial margin required with the latest mark price

Example: 0.00000000

maxWithdrawAmount

string

maximum amount for transfer out

Example: 0.00241969

crossWalletBalance

string

wallet balance for crossed margin

Example: 0.00241969

crossUnPnl

string

total unrealized profit or loss of crossed positions

Example: 0.00000000

availableBalance

string

available margin balance

Example: 0.00241969

updateTime

integer · int64

update time

Example: 1625474304765

object[]

Position list.

symbol

string

Trading symbol

Example: BTCUSD_201225

positionAmt

string

position amount

Example: 0

initialMargin

string

total intial margin required with the latest mark price

Example: 0

maintMargin

string

maintenance margin

Example: 0

unrealizedProfit

string

unrealized profit or loss

Example: 0.00000000

positionInitialMargin

string

positions" margin required with the latest mark price

Example: 0

openOrderInitialMargin

string

open orders" intial margin required with the latest mark price

Example: 0

leverage

string

Leverage value.

Example: 125

isolated

boolean

Whether isolated margin mode is enabled.

Example: false

positionSide

string

Position side

Example: BOTH

entryPrice

string

Position entry price.

Example: 0.0

breakEvenPrice

string

break-even price

Example: 0.0

maxQty

string

maximum quantity of base asset

Example: 50

updateTime

integer · int64

update time

Example: 0

notionalValue

string

Notional value.

Example: 0

canDeposit

boolean

Whether deposits are enabled.

Example: true

canTrade

boolean

Whether trading is enabled.

Example: true

canWithdraw

boolean

Whether withdrawals are enabled.

Example: true

feeTier

integer · int64

Fee tier level.

Example: 2

updateTime

integer · int64

update time

Example: 0

GET/dapi/v1/account

curl --request GET \
  --url 'https://dapi.binance.com/dapi/v1/account?timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

{
  "assets": [
    {
      "asset": "BTC",
      "walletBalance": "0.00241969",
      "unrealizedProfit": "0.00000000",
      "marginBalance": "0.00241969",
      "maintMargin": "0.00000000",
      "initialMargin": "0.00000000",
      "positionInitialMargin": "0.00000000",
      "openOrderInitialMargin": "0.00000000",
      "maxWithdrawAmount": "0.00241969",
      "crossWalletBalance": "0.00241969",
      "crossUnPnl": "0.00000000",
      "availableBalance": "0.00241969",
      "updateTime": 1625474304765
    }
  ],
  "positions": [
    {
      "symbol": "BTCUSD_201225",
      "positionAmt": "0",
      "initialMargin": "0",
      "maintMargin": "0",
      "unrealizedProfit": "0.00000000",
      "positionInitialMargin": "0",
      "openOrderInitialMargin": "0",
      "leverage": "125",
      "isolated": false,
      "positionSide": "BOTH",
      "entryPrice": "0.0",
      "breakEvenPrice": "0.0",
      "maxQty": "50",
      "updateTime": 0,
      "notionalValue": "0"
    }
  ],
  "canDeposit": true,
  "canTrade": true,
  "canWithdraw": true,
  "feeTier": 2,
  "updateTime": 0
}

json

application/json

Futures Account Balance (USER_DATA)

Check futures account balance

GET

/dapi/v1/balance

https://dapi.binance.com

Futures Account Balance (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 Account Balance (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 Account Balance (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 Account Balance (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

Futures Account Balance (USER_DATA) › Responses

200

Futures Account Balance

object

accountAlias

string

unique account code

Example: SgsR

asset

string

asset name

Example: BTC

balance

string

Account balance.

Example: 0.00250000

withdrawAvailable

string

Available amount for withdrawal.

Example: 0.00250000

crossWalletBalance

string

wallet balance for crossed margin

Example: 0.00241969

crossUnPnl

string

total unrealized profit or loss of crossed positions

Example: 0.00000000

availableBalance

string

available margin balance

Example: 0.00241969

updateTime

integer · int64

update time

Example: 1592468353979

Get Current Position Mode (USER_DATA)

Get user's position mode (Hedge Mode or One-way Mode ) on EVERY symbol

GET

/dapi/v1/positionSide/dual

https://dapi.binance.com

Get Current Position Mode (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 Current Position Mode (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 Weight30

Get Current Position Mode (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 Current Position Mode (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 Current Position Mode (USER_DATA) › Responses

200

Get Current Position Mode

dualSidePosition

boolean

Whether dual-side position mode is enabled.

Example: true

Get Download Id For Futures Order History (USER_DATA)

Get Download Id For Futures Order History

GET

/dapi/v1/order/asyn

https://dapi.binance.com

Get Download Id For Futures Order History (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 Download Id For Futures Order History (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 Weight1000

Get Download Id For Futures Order History (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 Download Id For Futures Order History (USER_DATA) › Query Parameters

startTime

integer · int64 · required

Timestamp in ms

Example: 1623319461670

endTime

integer · int64 · required

Timestamp in ms

Example: 1641782889000

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 Download Id For Futures Order History (USER_DATA) › Responses

200

Get Download Id For Futures Order History

avgCostTimestampOfLast30d

integer · int64

Average time taken for data download in the past 30 days

Example: 7241837

downloadId

string

Download task ID.

Example: 546975389218332672

Get Download Id For Futures Trade History (USER_DATA)

Get download id for futures trade history

GET

/dapi/v1/trade/asyn

https://dapi.binance.com

Get Download Id For Futures Trade History (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 Download Id For Futures Trade History (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 Weight1000

Get Download Id For Futures Trade History (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 Download Id For Futures Trade History (USER_DATA) › Query Parameters

startTime

integer · int64 · required

Timestamp in ms

Example: 1623319461670

endTime

integer · int64 · required

Timestamp in ms

Example: 1641782889000

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 Download Id For Futures Trade History (USER_DATA) › Responses

200

Get Download Id For Futures Trade History

avgCostTimestampOfLast30d

integer · int64

Average time taken for data download in the past 30 days

Example: 7241837

downloadId

string

Download task ID.

Example: 546975389218332672

Get Download Id For Futures Transaction History (USER_DATA)

Get download id for futures transaction history

GET

/dapi/v1/income/asyn

https://dapi.binance.com

Get Download Id For Futures Transaction History (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 Download Id For Futures Transaction History (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 Weight1000

Get Download Id For Futures Transaction History (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 Download Id For Futures Transaction History (USER_DATA) › Query Parameters

startTime

integer · int64 · required

Timestamp in ms

Example: 1623319461670

endTime

integer · int64 · required

Timestamp in ms

Example: 1641782889000

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 Download Id For Futures Transaction History (USER_DATA) › Responses

200

Get Download Id For Futures Transaction History

avgCostTimestampOfLast30d

integer · int64

Average time taken for data download in the past 30 days

Example: 7241837

downloadId

string

Download task ID.

Example: 546975389218332672

Get Futures Order History Download Link by Id (USER_DATA)

Get futures order history download link by Id

GET

/dapi/v1/order/asyn/id

https://dapi.binance.com

Get Futures Order History Download Link by Id (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 Order History Download Link by Id (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 Weight5

Get Futures Order History Download Link by Id (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 Order History Download Link by Id (USER_DATA) › Query Parameters

downloadId

string · required

get by download id api

Example: 545923594199212032

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 Order History Download Link by Id (USER_DATA) › Responses

200

Get Futures Order History Download Link by Id

downloadId

string

Download task ID.

Example: 545923594199212032

status

string

Enum：completed，processing

Example: processing

url

string

The link is mapped to download id

Example:

notified

boolean

ignore

Example: false

expirationTimestamp

integer · int64

The link would expire after this timestamp

Example: -1

isExpired

string

Whether the record is expired.

Example: null

Get Futures Trade Download Link by Id (USER_DATA)

Get futures trade download link by Id

GET

/dapi/v1/trade/asyn/id

https://dapi.binance.com

Get Futures Trade Download Link by Id (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 Trade Download Link by Id (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 Weight5

Get Futures Trade Download Link by Id (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 Trade Download Link by Id (USER_DATA) › Query Parameters

downloadId

string · required

get by download id api

Example: 545923594199212032

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 Trade Download Link by Id (USER_DATA) › Responses

200

Get Futures Trade Download Link by Id

downloadId

string

Download task ID.

Example: 545923594199212032

status

string

Enum：completed，processing

Example: processing

url

string

The link is mapped to download id

Example:

notified

boolean

ignore

Example: false

expirationTimestamp

integer · int64

The link would expire after this timestamp

Example: -1

isExpired

string

Whether the record is expired.

Example: null

Get Futures Transaction History Download Link by Id (USER_DATA)

Get futures transaction history download link by Id

GET

/dapi/v1/income/asyn/id

https://dapi.binance.com

Get Futures Transaction History Download Link by Id (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 Transaction History Download Link by Id (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 Weight5

Get Futures Transaction History Download Link by Id (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 Transaction History Download Link by Id (USER_DATA) › Query Parameters

downloadId

string · required

get by download id api

Example: 545923594199212032

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 Transaction History Download Link by Id (USER_DATA) › Responses

200

Get Futures Transaction History Download Link by Id

downloadId

string

Download task ID.

Example: 545923594199212032

status

string

Enum：completed，processing

Example: processing

url

string

The link is mapped to download id

Example:

notified

boolean

ignore

Example: false

expirationTimestamp

integer · int64

The link would expire after this timestamp

Example: -1

isExpired

string

Whether the record is expired.

Example: null

Get Income History (USER_DATA)

Get income history

GET

/dapi/v1/income

https://dapi.binance.com

Get Income History (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 Income History (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 Weight20

Get Income History (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 Income History (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

symbol

string

Symbol

Example: BTCUSDT

incomeType

string · enum

Income type.

Enum values:

TRANSFER

WELCOME_BONUS

FUNDING_FEE

REALIZED_PNL

COMMISSION

INSURANCE_CLEAR

DELIVERED_SETTELMENT

Example: TRANSFER

startTime

integer · int64

Timestamp in ms to get funding from INCLUSIVE.

Example: 1623319461670

endTime

integer · int64

Timestamp in ms to get funding until INCLUSIVE.

Example: 1641782889000

page

integer · int64

Page number

Example: 1

limit

integer · int64 · max: 1000

Maximum number of records to return.

Example: 30

Default: 100

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Income History (USER_DATA) › Responses

200

Get Income History

object

symbol

string

Trading symbol

Example:

incomeType

string

income type

Example: TRANSFER

income

string

income amount

Example: -0.37500000

asset

string

asset name

Example: BTC

info

string

extra information

Example: WITHDRAW

time

integer · int64

Time

Example: 1570608000000

tranId

string

transaction id

Example: 9689322392

tradeId

string

Trade ID.

Example:

Notional Bracket for Pair (USER_DATA)

Not recommended to continue using this v1 endpoint

Get the pair's default notional bracket list, may return ambiguous values when there have been multiple different symbol brackets under the pair, suggest using the following GET /dapi/v2/leverageBracket query instead to get the specific symbol notional bracket list.

GET

/dapi/v1/leverageBracket

https://dapi.binance.com

Notional Bracket for Pair (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

Notional Bracket for Pair (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

Notional Bracket for Pair (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

Notional Bracket for Pair (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

pair

string

Example: BTCUSD

recvWindow

integer · int64 · max: 60000

Example: 5000

Notional Bracket for Pair (USER_DATA) › Responses

200

Notional Bracket for Pair

object

pair

string

Pair

Example: BTCUSD

object[]

Leverage bracket details.

bracket

integer · int64

bracket level

Example: 1

initialLeverage

integer · int64

the maximum leverage

Example: 125

qtyCap

integer · int64

upper edge of base asset quantity

Example: 50

qtylFloor

integer · int64

lower edge of base asset quantity

Example: 0

maintMarginRatio

number · float

Maintenance margin ratio.

Example: 0.004

cum

number · float

Cumulative value.

Example: 0

Notional Bracket for Symbol (USER_DATA)

Get the symbol's notional bracket list.

GET

/dapi/v2/leverageBracket

https://dapi.binance.com

Notional Bracket for Symbol (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

Notional Bracket for Symbol (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 Weight

1 (after CM migration: 1 with symbol / 2 without symbol)

Notional Bracket for Symbol (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

Notional Bracket for Symbol (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

symbol

string

Example: BTCUSD_PERP

recvWindow

integer · int64 · max: 60000

Example: 5000

Notional Bracket for Symbol (USER_DATA) › Responses

200

Notional Bracket for Symbol

object

symbol

string

Trading symbol

Example: BTCUSD_PERP

notionalCoef

number · float

user symbol bracket multiplier, only appears when user's symbol bracket is adjusted

Example: 1.5

object[]

Leverage bracket details.

bracket

integer · int64

bracket level

Example: 1

initialLeverage

integer · int64

the maximum leverage

Example: 125

qtyCap

integer · int64

upper edge of base asset quantity

Example: 50

qtylFloor

integer · int64

lower edge of base asset quantity

Example: 0

maintMarginRatio

number · float

Maintenance margin ratio.

Example: 0.004

cum

number · float

Cumulative value.

Example: 0

User Commission Rate (USER_DATA)

Query user commission rate

GET

/dapi/v1/commissionRate

https://dapi.binance.com

User Commission Rate (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

User Commission Rate (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 Weight20

User Commission Rate (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

User Commission Rate (USER_DATA) › Query Parameters

symbol

string · required

Symbol

Example: BTCUSD_PERP

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

User Commission Rate (USER_DATA) › Responses

200

User Commission Rate

symbol

string

Trading symbol

Example: BTCUSD_PERP

makerCommissionRate

string

0.015%

Example: 0.00015

takerCommissionRate

string

Taker commission rate.

Example: 0.00040