Trade

Endpoint

Change Position Mode (TRADE)

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

After CM migration, UM and CM share the same dualSidePosition setting. Calling this endpoint flips both UM and CM at once. If either side has any open order or open position, the change is rejected:

-4067 (open orders exist)
-4068 (open position exists)

POST

/dapi/v1/positionSide/dual

https://dapi.binance.com

Change Position Mode (TRADE) › 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

Change Position Mode (TRADE) › 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

Change Position Mode (TRADE) › 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

Change Position Mode (TRADE) › Request Body

dualSidePosition

string · required

"true": Hedge Mode; "false": One-way Mode

Example: true

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

Change Position Mode (TRADE) › Responses

200

Change Position Mode

code

integer · int64

API response code. "000000" indicates success.

Example: 200

msg

string

Message details.

Example: success

Account Trade List (USER_DATA)

Get trades for a specific account and symbol.

GET

/dapi/v1/userTrades

https://dapi.binance.com

Account Trade List (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 Trade List (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

20 with symbol，40 with pair (after CM migration: 5 flat)

Account Trade List (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 Trade List (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: BTCUSD_200626

pair

string

pair

Example: BTCUSD

orderId

string

Order ID

Example: 1

startTime

integer · int64

Start time

Example: 1623319461670

endTime

integer · int64

End time

Example: 1641782889000

fromId

integer · int64

Trade id to fetch from. Default gets most recent trades.

Example: 6

limit

integer · int64 · max: 1000

Maximum number of records to return.

Example: 30

Default: 50

recvWindow

integer · int64 · max: 60000

Example: 5000

Account Trade List (USER_DATA) › Responses

200

Account Trade List

object

symbol

string

Trading symbol

Example: BTCUSD_200626

id

integer · int64

positionId

Example: 6

orderId

integer · int64

Sub-order ID

Example: 28

pair

string

Pair

Example: BTCUSD

side

string

Trading side

Example: SELL

price

string

Latest token price.

Example: 8800

qty

string

Quantity.

Example: 1

realizedPnl

string

Realized PnL.

Example: 0

marginAsset

string

Margin asset.

Example: BTC

baseQty

string

Base asset quantity.

Example: 0.01136364

commission

string

Transaction Fee (in Crypto)

Example: 0.00000454

commissionAsset

string

Commission asset.

Example: BTC

time

integer · int64

Time

Example: 1590743483586

positionSide

string

Position side

Example: BOTH

buyer

boolean

Whether the trade is a buy side for the account.

Example: false

maker

boolean

Whether the account is maker in this trade.

Example: false

All Orders (USER_DATA)

Get all account orders; active, canceled, or filled.

These orders will not be found:
- order status is CANCELED or EXPIRED AND order has NO filled trade AND created time + 3 days < current time
- order create time + 90 days < current time

GET

/dapi/v1/allOrders

https://dapi.binance.com

All Orders (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

All Orders (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

20 with symbol, 40 with pair (after CM migration: 5 flat)

All Orders (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

All Orders (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: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

orderId

integer · int64

Example: 1917641

startTime

integer · int64

Start time

Example: 1623319461670

endTime

integer · int64

End time

Example: 1641782889000

limit

integer · int64 · max: 100

Maximum number of records to return.

Example: 30

Default: 50

recvWindow

integer · int64 · max: 60000

Example: 5000

All Orders (USER_DATA) › Responses

200

All Orders

object

avgPrice

string

Average execution price

Example: 0.0

clientOrderId

string

Client order ID.

Example: abc

cumBase

string

Cumulative base asset amount.

Example: 0

executedQty

string

Executed quantity

Example: 0

orderId

integer · int64

Sub-order ID

Example: 1917641

origQty

string

Original order quantity

Example: 0.40

origType

string

Original order type.

Example: TRAILING_STOP_MARKET

price

string

Latest token price.

Example: 0

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

side

string

Trading side

Example: BUY

positionSide

string

Position side

Example: SHORT

status

string

Enum：completed，processing

Example: NEW

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 9300

closePosition

boolean

if Close-All

Example: false

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

time

integer · int64

Time

Example: 1579276756075

timeInForce

string

Time in force

Example: GTC

type

string

Order type.

Example: TRAILING_STOP_MARKET

activatePrice

string

activation price, only return with TRAILING_STOP_MARKET order

Example: 9020

priceRate

string

callback rate, only return with TRAILING_STOP_MARKET order

Example: 0.3

updateTime

integer · int64

update time

Example: 1579276756075

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

GET/dapi/v1/allOrders

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

Example Responses

[
  {
    "avgPrice": "0.0",
    "clientOrderId": "abc",
    "cumBase": "0",
    "executedQty": "0",
    "orderId": 1917641,
    "origQty": "0.40",
    "origType": "TRAILING_STOP_MARKET",
    "price": "0",
    "reduceOnly": false,
    "side": "BUY",
    "positionSide": "SHORT",
    "status": "NEW",
    "stopPrice": "9300",
    "closePosition": false,
    "symbol": "BTCUSD_200925",
    "pair": "BTCUSD",
    "time": 1579276756075,
    "timeInForce": "GTC",
    "type": "TRAILING_STOP_MARKET",
    "activatePrice": "9020",
    "priceRate": "0.3",
    "updateTime": 1579276756075,
    "workingType": "CONTRACT_PRICE",
    "priceProtect": false,
    "priceMatch": "NONE",
    "selfTradePreventionMode": "NONE"
  }
]

json

application/json

Auto-Cancel All Open Orders (TRADE)

Cancel all open orders of the specified symbol at the end of the specified countdown. This rest endpoint means to ensure your open orders are canceled in case of an outage. The endpoint should be called repeatedly as heartbeats so that the existing countdown time can be canceled and repalced by a new one. The system will check all countdowns approximately every 10 milliseconds, so please note that sufficient redundancy should be considered when using this function. We do not recommend setting the countdown time to be too precise or too small.

Example usage:

Call this endpoint at 30s intervals with an countdownTime of 120000 (120s).

If this endpoint is not called within 120 seconds, all your orders of the specified symbol will be automatically canceled.

If this endpoint is called with an countdownTime of 0, the countdown timer will be stopped.

POST

/dapi/v1/countdownCancelAll

https://dapi.binance.com

Auto-Cancel All Open Orders (TRADE) › 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

Auto-Cancel All Open Orders (TRADE) › 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

Auto-Cancel All Open Orders (TRADE) › 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

Auto-Cancel All Open Orders (TRADE) › Request Body

symbol

string · required

Example: BTCUSD_200925

countdownTime

integer · int64 · required

countdown time, 1000 for 1 second. 0 to cancel the timer

Example: 1000

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

Auto-Cancel All Open Orders (TRADE) › Responses

200

Auto-Cancel All Open Orders

symbol

string

Trading symbol

Example: BTCUSD_200925

countdownTime

string

Countdown cancellation time in milliseconds.

Example: 100000

Cancel All Open Orders (TRADE)

Cancel All Open Orders

DELETE

/dapi/v1/allOpenOrders

https://dapi.binance.com

Cancel All Open Orders (TRADE) › 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

Cancel All Open Orders (TRADE) › 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

Cancel All Open Orders (TRADE) › 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

Cancel All Open Orders (TRADE) › Query Parameters

symbol

string · required

Symbol

Example: BTCUSD_200925

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

Cancel All Open Orders (TRADE) › Responses

200

Cancel All Open Orders

code

integer · int64

API response code. "000000" indicates success.

Example: 200

msg

string

Message details.

Example: The operation of cancel all open order is done.

Modify Multiple Orders (TRADE)

Modify Multiple Orders

PUT

/dapi/v1/batchOrders

https://dapi.binance.com

Modify Multiple Orders (TRADE) › 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

Modify Multiple Orders (TRADE) › 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

Modify Multiple Orders (TRADE) › 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

Modify Multiple Orders (TRADE) › Request Body

object[] · required

order list. Max 5 orders

symbol

string · required

Trading symbol

Example: BTCUSD_PERP

side

string · enum · required

Trading side

Enum values:

BUY

SELL

Example: BUY

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

orderId

integer · int64

Sub-order ID, required when clientOrderId is not sent.

Example: 20072994037

origClientOrderId

string

Client order ID, required when orderId is not sent. Only support letters, numbers and underscores, and must be unique within 24 hours.

Example: LJ9R4QZDihCaS8UAOOLpgW

quantity

number · float

Order quantity, cannot be sent with closePosition=true. After CM migration, this parameter becomes mandatory (each batch element must send both price and quantity).

Example: 1

price

number · float

Latest token price. After CM migration, this parameter becomes mandatory (each batch element must send both price and quantity).

Example: 30005

recvWindow

integer · int64 · max: 60000

Example: 5000

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

Modify Multiple Orders (TRADE) › Responses

200

Modify Multiple Orders

object

orderId

integer · int64

Sub-order ID

Example: 20072994037

symbol

string

Trading symbol

Example: BTCUSD_PERP

pair

string

Pair

Example: BTCUSD

status

string

Enum：completed，processing

Example: NEW

clientOrderId

string

Client order ID.

Example: LJ9R4QZDihCaS8UAOOLpgW

price

string

Latest token price.

Example: 30005

origQty

string

Original order quantity

Example: 1

executedQty

string

Executed quantity

Example: 0

cumQty

string

Cumulative filled quantity.

Example: 0

timeInForce

string

Time in force

Example: GTC

type

string

Order type.

Example: LIMIT

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

closePosition

boolean

if Close-All

Example: false

side

string

Trading side

Example: BUY

positionSide

string

Position side

Example: LONG

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 0

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

origType

string

Original order type.

Example: LIMIT

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

updateTime

integer · int64

update time

Example: 1629182711600

code

integer · int64

API response code. "000000" indicates success.

Example: -2022

msg

string

Message details.

Example: ReduceOnly Order is rejected.

PUT/dapi/v1/batchOrders

curl --request PUT \
  --url https://dapi.binance.com/dapi/v1/batchOrders \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data 'batchOrders={"symbol":"BTCUSD_PERP","side":"BUY","timestamp":1770736694138}' \
  --data timestamp=1770736694138

Example Request Body

{
  "batchOrders": [
    {
      "symbol": "BTCUSD_PERP",
      "side": "BUY",
      "timestamp": 1770736694138
    }
  ],
  "timestamp": 1770736694138
}

json

Example Responses

[
  {
    "orderId": 20072994037,
    "symbol": "BTCUSD_PERP",
    "pair": "BTCUSD",
    "status": "NEW",
    "clientOrderId": "LJ9R4QZDihCaS8UAOOLpgW",
    "price": "30005",
    "origQty": "1",
    "executedQty": "0",
    "cumQty": "0",
    "timeInForce": "GTC",
    "type": "LIMIT",
    "reduceOnly": false,
    "closePosition": false,
    "side": "BUY",
    "positionSide": "LONG",
    "stopPrice": "0",
    "workingType": "CONTRACT_PRICE",
    "priceProtect": false,
    "origType": "LIMIT",
    "priceMatch": "NONE",
    "selfTradePreventionMode": "NONE",
    "updateTime": 1629182711600,
    "code": -2022,
    "msg": "ReduceOnly Order is rejected."
  }
]

json

application/json

Place Multiple Orders (TRADE)

Place multiple orders

Parameter rules are same with New Order
Batch orders are processed concurrently, and the order of matching is not guaranteed.
The order of returned contents for batch orders is the same as the order of the order list.

POST

/dapi/v1/batchOrders

https://dapi.binance.com

Place Multiple Orders (TRADE) › 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

Place Multiple Orders (TRADE) › 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

Place Multiple Orders (TRADE) › 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

Place Multiple Orders (TRADE) › Request Body

object[] · required

order list. Max 5 orders

symbol

string · required

Symbol

Example: BTCUSD_PERP

side

string · enum · required

Enum values:

BUY

SELL

Example: BUY

type

string · enum · required

After CM migration, stop-type values (STOP, STOP_MARKET, TAKE_PROFIT, TAKE_PROFIT_MARKET, TRAILING_STOP_MARKET) are no longer accepted on a per-element basis and will return element-level -4120. Use the new /dapi/v1/algoOrder endpoint instead.

Enum values:

LIMIT

MARKET

STOP

STOP_MARKET

TAKE_PROFIT

TAKE_PROFIT_MARKET

TRAILING_STOP_MARKET

Example: LIMIT

quantity

number · float · required

quantity measured by contract number

Example: 1

positionSide

string · enum

Default BOTH for One-way Mode ; LONG or SHORT for Hedge Mode. It must be sent with Hedge Mode.

Enum values:

BOTH

LONG

SHORT

Example: BOTH

timeInForce

string · enum

Enum values:

GTC

IOC

FOK

GTX

Example: GTC

reduceOnly

string · enum

Enum values:

true

false

Example: true

Default: false

price

number · float

Order price

Example: 10001

newClientOrderId

string

A unique id among open orders. Automatically generated if not sent. Can only be string following the rule: ^[\.A-Z\:/a-z0-9_-]{1,36}$

Example: 1

stopPrice

number · float

Used with STOP/STOP_MARKET or TAKE_PROFIT/TAKE_PROFIT_MARKET orders.

Example: 9000

activationPrice

number · float

Used with TRAILING_STOP_MARKET orders, default as the latest price(supporting different workingType)

Example: 9020

callbackRate

number · float · min: 0.1 · max: 4

Used with TRAILING_STOP_MARKET orders, min 0.1, max 4 where 1 for 1%

Example: 1

workingType

string · enum

Enum values:

MARK_PRICE

CONTRACT_PRICE

Example: MARK_PRICE

Default: CONTRACT_PRICE

priceProtect

string · enum

Used with STOP/STOP_MARKET or TAKE_PROFIT/TAKE_PROFIT_MARKET orders.

Enum values:

true

false

Example: false

Default: false

newOrderRespType

string · enum

Enum values:

ACK

RESULT

Example: ACK

Default: ACK

priceMatch

string · enum

only avaliable for LIMIT/STOP/TAKE_PROFIT order; can't be passed together with price

Enum values:

OPPONENT

OPPONENT_5

OPPONENT_10

OPPONENT_20

QUEUE

QUEUE_5

QUEUE_10

QUEUE_20

Example: OPPONENT

selfTradePreventionMode

string · enum

EXPIRE_TAKER taker order when STP triggers/ EXPIRE_MAKER taker order when STP triggers/ EXPIRE_BOTH both orders when STP triggers

Enum values:

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

Example: EXPIRE_TAKER

Default: EXPIRE_MAKER

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

Place Multiple Orders (TRADE) › Responses

200

Place Multiple Orders

object

clientOrderId

string

Client order ID.

Example: testOrder

cumQty

string

Cumulative filled quantity.

Example: 0

executedQty

string

Executed quantity

Example: 0

orderId

integer · int64

Sub-order ID

Example: 22542179

origQty

string

Original order quantity

Example: 10

price

string

Latest token price.

Example: 0

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

side

string

Trading side

Example: SELL

positionSide

string

Position side

Example: SHORT

status

string

Enum：completed，processing

Example: NEW

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 0

closePosition

boolean

if Close-All

Example: false

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

timeInForce

string

Time in force

Example: GTC

type

string

Order type.

Example: TRAILING_STOP_MARKET

origType

string

Original order type.

Example: TRAILING_STOP_MARKET

activatePrice

string

activation price, only return with TRAILING_STOP_MARKET order

Example: 9020

priceRate

string

callback rate, only return with TRAILING_STOP_MARKET order

Example: 0.3

updateTime

integer · int64

update time

Example: 1566818724722

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

code

integer · int64

API response code. "000000" indicates success.

Example: -2022

msg

string

Message details.

Example: ReduceOnly Order is rejected.

POST/dapi/v1/batchOrders

curl --request POST \
  --url https://dapi.binance.com/dapi/v1/batchOrders \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data 'batchOrders={"symbol":"BTCUSD_PERP","side":"BUY","type":"LIMIT","quantity":1}' \
  --data timestamp=1770736694138

Example Request Body

{
  "batchOrders": [
    {
      "symbol": "BTCUSD_PERP",
      "side": "BUY",
      "type": "LIMIT",
      "quantity": 1
    }
  ],
  "timestamp": 1770736694138
}

json

Example Responses

[
  {
    "clientOrderId": "testOrder",
    "cumQty": "0",
    "executedQty": "0",
    "orderId": 22542179,
    "origQty": "10",
    "price": "0",
    "reduceOnly": false,
    "side": "SELL",
    "positionSide": "SHORT",
    "status": "NEW",
    "stopPrice": "0",
    "closePosition": false,
    "symbol": "BTCUSD_200925",
    "pair": "BTCUSD",
    "timeInForce": "GTC",
    "type": "TRAILING_STOP_MARKET",
    "origType": "TRAILING_STOP_MARKET",
    "activatePrice": "9020",
    "priceRate": "0.3",
    "updateTime": 1566818724722,
    "workingType": "CONTRACT_PRICE",
    "priceProtect": false,
    "priceMatch": "NONE",
    "selfTradePreventionMode": "NONE",
    "code": -2022,
    "msg": "ReduceOnly Order is rejected."
  }
]

json

application/json

Cancel Multiple Orders (TRADE)

Cancel Multiple Orders

DELETE

/dapi/v1/batchOrders

https://dapi.binance.com

Cancel Multiple Orders (TRADE) › 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

Cancel Multiple Orders (TRADE) › 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

Cancel Multiple Orders (TRADE) › 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

Cancel Multiple Orders (TRADE) › Query Parameters

symbol

string · required

Symbol

Example: BTCUSD_200925

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

orderIdList

integer[] · maxItems: 10

Order IDs to cancel.

Example: [1234567,2345678]

origClientOrderIdList

string[] · maxItems: 10

Original client order IDs to cancel.

Example: ["my_id_1","my_id_2"]

recvWindow

integer · int64 · max: 60000

Example: 5000

Cancel Multiple Orders (TRADE) › Responses

200

Cancel Multiple Orders

object

clientOrderId

string

Client order ID.

Example: myOrder1

cumQty

string

Cumulative filled quantity.

Example: 0

executedQty

string

Executed quantity

Example: 0

orderId

integer · int64

Sub-order ID

Example: 283194212

origQty

string

Original order quantity

Example: 11

price

string

Latest token price.

Example: 0

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

side

string

Trading side

Example: BUY

positionSide

string

Position side

Example: SHORT

status

string

Enum：completed，processing

Example: CANCELED

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 9300

closePosition

boolean

if Close-All

Example: false

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

timeInForce

string

Time in force

Example: GTC

origType

string

Original order type.

Example: TRAILING_STOP_MARKET

type

string

Order type.

Example: TRAILING_STOP_MARKET

activatePrice

string

activation price, only return with TRAILING_STOP_MARKET order

Example: 9020

priceRate

string

callback rate, only return with TRAILING_STOP_MARKET order

Example: 0.3

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

updateTime

integer · int64

update time

Example: 1571110484038

code

integer · int64

API response code. "000000" indicates success.

Example: -2011

msg

string

Message details.

Example: Unknown order sent.

DELETE/dapi/v1/batchOrders

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

Example Responses

[
  {
    "clientOrderId": "myOrder1",
    "cumQty": "0",
    "executedQty": "0",
    "orderId": 283194212,
    "origQty": "11",
    "price": "0",
    "reduceOnly": false,
    "side": "BUY",
    "positionSide": "SHORT",
    "status": "CANCELED",
    "stopPrice": "9300",
    "closePosition": false,
    "symbol": "BTCUSD_200925",
    "pair": "BTCUSD",
    "timeInForce": "GTC",
    "origType": "TRAILING_STOP_MARKET",
    "type": "TRAILING_STOP_MARKET",
    "activatePrice": "9020",
    "priceRate": "0.3",
    "workingType": "CONTRACT_PRICE",
    "priceProtect": false,
    "priceMatch": "NONE",
    "selfTradePreventionMode": "NONE",
    "updateTime": 1571110484038,
    "code": -2011,
    "msg": "Unknown order sent."
  }
]

json

application/json

Query Order (USER_DATA)

Check an order's status.

These orders will not be found:
- order status is CANCELED or EXPIRED AND order has NO filled trade AND created time + 3 days < current time
- order create time + 90 days < current time

GET

/dapi/v1/order

https://dapi.binance.com

Query Order (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 Order (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 Order (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 Order (USER_DATA) › Query Parameters

symbol

string · required

Symbol

Example: BTCUSD_200925

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

orderId

integer · int64

Order ID

Example: 1

origClientOrderId

string

Client order ID

Example: 1

recvWindow

integer · int64 · max: 60000

Example: 5000

Query Order (USER_DATA) › Responses

200

Order

avgPrice

string

Average execution price

Example: 0.0

clientOrderId

string

Client order ID.

Example: abc

cumBase

string

Cumulative base asset amount.

Example: 0

executedQty

string

Executed quantity

Example: 0

orderId

integer · int64

Sub-order ID

Example: 1573346959

origQty

string

Original order quantity

Example: 0.40

origType

string

Original order type.

Example: TRAILING_STOP_MARKET

price

string

Latest token price.

Example: 0

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

side

string

Trading side

Example: BUY

positionSide

string

Position side

Example: SHORT

status

string

Enum：completed，processing

Example: NEW

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 9300

closePosition

boolean

if Close-All

Example: false

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

time

integer · int64

Time

Example: 1579276756075

timeInForce

string

Time in force

Example: GTC

type

string

Order type.

Example: TRAILING_STOP_MARKET

activatePrice

string

activation price, only return with TRAILING_STOP_MARKET order

Example: 9020

priceRate

string

callback rate, only return with TRAILING_STOP_MARKET order

Example: 0.3

updateTime

integer · int64

update time

Example: 1579276756075

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

GET/dapi/v1/order

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

Example Responses

{
  "avgPrice": "0.0",
  "clientOrderId": "abc",
  "cumBase": "0",
  "executedQty": "0",
  "orderId": 1573346959,
  "origQty": "0.40",
  "origType": "TRAILING_STOP_MARKET",
  "price": "0",
  "reduceOnly": false,
  "side": "BUY",
  "positionSide": "SHORT",
  "status": "NEW",
  "stopPrice": "9300",
  "closePosition": false,
  "symbol": "BTCUSD_200925",
  "pair": "BTCUSD",
  "time": 1579276756075,
  "timeInForce": "GTC",
  "type": "TRAILING_STOP_MARKET",
  "activatePrice": "9020",
  "priceRate": "0.3",
  "updateTime": 1579276756075,
  "workingType": "CONTRACT_PRICE",
  "priceProtect": false,
  "priceMatch": "NONE",
  "selfTradePreventionMode": "NONE"
}

json

application/json

Modify Order (TRADE)

Order modify function, currently only LIMIT order modification is supported, modified orders will be reordered in the match queue

PUT

/dapi/v1/order

https://dapi.binance.com

Modify Order (TRADE) › 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

Modify Order (TRADE) › 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

Modify Order (TRADE) › 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

Modify Order (TRADE) › Request Body

symbol

string · required

Symbol

Example: BTCUSD_PERP

side

string · enum · required

Enum values:

BUY

SELL

Example: BUY

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

orderId

integer · int64

Order ID

Example: 1

origClientOrderId

string

Client order ID

Example: 1

quantity

number · float

Order quantity, cannot be sent with closePosition=true. After CM migration, this parameter becomes mandatory (must be sent together with price).

Example: 1.0

price

number · float

Order price. After CM migration, this parameter becomes mandatory (must be sent together with quantity).

Example: 1.0

priceMatch

string · enum

only avaliable for LIMIT/STOP/TAKE_PROFIT order; Can't be passed together with price

Enum values:

OPPONENT

OPPONENT_5

OPPONENT_10

OPPONENT_20

QUEUE

QUEUE_5

QUEUE_10

QUEUE_20

Example: OPPONENT

recvWindow

integer · int64 · max: 60000

Example: 5000

Modify Order (TRADE) › Responses

200

Modify Order

orderId

integer · int64

Sub-order ID

Example: 20072994037

symbol

string

Trading symbol

Example: BTCUSD_PERP

pair

string

Pair

Example: BTCUSD

status

string

Enum：completed，processing

Example: NEW

clientOrderId

string

Client order ID.

Example: LJ9R4QZDihCaS8UAOOLpgW

price

string

Latest token price.

Example: 30005

origQty

string

Original order quantity

Example: 1

executedQty

string

Executed quantity

Example: 0

cumQty

string

Cumulative filled quantity.

Example: 0

timeInForce

string

Time in force

Example: GTC

type

string

Order type.

Example: LIMIT

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

closePosition

boolean

if Close-All

Example: false

side

string

Trading side

Example: BUY

positionSide

string

Position side

Example: LONG

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 0

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

origType

string

Original order type.

Example: LIMIT

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

updateTime

integer · int64

update time

Example: 1629182711600

PUT/dapi/v1/order

curl --request PUT \
  --url https://dapi.binance.com/dapi/v1/order \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BTCUSD_PERP \
  --data side=BUY \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BTCUSD_PERP",
  "side": "BUY",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "orderId": 20072994037,
  "symbol": "BTCUSD_PERP",
  "pair": "BTCUSD",
  "status": "NEW",
  "clientOrderId": "LJ9R4QZDihCaS8UAOOLpgW",
  "price": "30005",
  "origQty": "1",
  "executedQty": "0",
  "cumQty": "0",
  "timeInForce": "GTC",
  "type": "LIMIT",
  "reduceOnly": false,
  "closePosition": false,
  "side": "BUY",
  "positionSide": "LONG",
  "stopPrice": "0",
  "workingType": "CONTRACT_PRICE",
  "priceProtect": false,
  "origType": "LIMIT",
  "priceMatch": "NONE",
  "selfTradePreventionMode": "NONE",
  "updateTime": 1629182711600
}

json

application/json

New Order (TRADE)

Send in a new order.

POST

/dapi/v1/order

https://dapi.binance.com

New Order (TRADE) › 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

New Order (TRADE) › 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 on 1min order rate limit(X-MBX-ORDER-COUNT-1M) 0 on IP rate limit(x-mbx-used-weight-1m)

New Order (TRADE) › 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

New Order (TRADE) › Request Body

symbol

string · required

Symbol

Example: BTCUSD_200925

side

string · enum · required

Enum values:

BUY

SELL

Example: BUY

type

string · enum · required

After CM migration, stop-type values (STOP, STOP_MARKET, TAKE_PROFIT, TAKE_PROFIT_MARKET, TRAILING_STOP_MARKET) are no longer accepted by this endpoint and will return -4120. Use the new /dapi/v1/algoOrder endpoint instead.

Enum values:

LIMIT

MARKET

STOP

STOP_MARKET

TAKE_PROFIT

TAKE_PROFIT_MARKET

TRAILING_STOP_MARKET

Example: LIMIT

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

positionSide

string · enum

Default BOTH for One-way Mode ; LONG or SHORT for Hedge Mode. It must be sent in Hedge Mode.

Enum values:

BOTH

LONG

SHORT

Example: BOTH

reduceOnly

string · enum

"true" or "false". Cannot be sent in Hedge Mode; cannot be sent with closePosition=true(Close-All)

Enum values:

true

false

Example: true

Default: false

quantity

number · float

quantity measured by contract number, Cannot be sent with closePosition=true

Example: 1.0

price

number · float

Order price

Example: 1.0

newClientOrderId

string

A unique id among open orders. Automatically generated if not sent. Can only be string following the rule: ^[\.A-Z\:/a-z0-9_-]{1,36}$

Example: 1

stopPrice

number · float

Used with STOP/STOP_MARKET or TAKE_PROFIT/TAKE_PROFIT_MARKET orders.

Example: 1.0

closePosition

string

true, false；Close-All,used with STOP_MARKET or TAKE_PROFIT_MARKET.

Example: true

activationPrice

number · float

Used with TRAILING_STOP_MARKET orders, default as the latest price(supporting different workingType)

Example: 1.0

callbackRate

number · float

Used with TRAILING_STOP_MARKET orders, min 0.1, max 10 where 1 for 1%

Example: 5000.0

timeInForce

string · enum

Enum values:

GTC

IOC

FOK

GTX

Example: GTC

workingType

string · enum

'stopPrice triggered by: "MARK_PRICE", "CONTRACT_PRICE".

Enum values:

MARK_PRICE

CONTRACT_PRICE

Example: MARK_PRICE

Default: CONTRACT_PRICE

priceProtect

string · enum

"true" or "false". Used with STOP/STOP_MARKET or TAKE_PROFIT/TAKE_PROFIT_MARKET orders.

Enum values:

true

false

Example: false

Default: false

newOrderRespType

string · enum

Enum values:

ACK

RESULT

Example: ACK

Default: ACK

priceMatch

string · enum

only avaliable for LIMIT/STOP/TAKE_PROFIT order; Can't be passed together with price

Enum values:

OPPONENT

OPPONENT_5

OPPONENT_10

OPPONENT_20

QUEUE

QUEUE_5

QUEUE_10

QUEUE_20

Example: OPPONENT

selfTradePreventionMode

string · enum

EXPIRE_TAKER taker order when STP triggers/ EXPIRE_MAKER taker order when STP triggers/ EXPIRE_BOTH both orders when STP triggers

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_BOTH

EXPIRE_MAKER

Example: EXPIRE_TAKER

Default: EXPIRE_MAKER

recvWindow

integer · int64 · max: 60000

Example: 5000

New Order (TRADE) › Responses

200

New Order

clientOrderId

string

Client order ID.

Example: testOrder

cumQty

string

Cumulative filled quantity.

Example: 0

executedQty

string

Executed quantity

Example: 0

orderId

integer · int64

Sub-order ID

Example: 22542179

origQty

string

Original order quantity

Example: 10

price

string

Latest token price.

Example: 0

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

closePosition

boolean

if Close-All

Example: false

side

string

Trading side

Example: SELL

positionSide

string

Position side

Example: SHORT

status

string

Enum：completed，processing

Example: NEW

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 0

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

timeInForce

string

Time in force

Example: GTC

type

string

Order type.

Example: TRAILING_STOP_MARKET

origType

string

Original order type.

Example: TRAILING_STOP_MARKET

activatePrice

string

activation price, only return with TRAILING_STOP_MARKET order

Example: 9020

priceRate

string

callback rate, only return with TRAILING_STOP_MARKET order

Example: 0.3

updateTime

integer · int64

update time

Example: 1566818724722

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

POST/dapi/v1/order

curl --request POST \
  --url https://dapi.binance.com/dapi/v1/order \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BTCUSD_200925 \
  --data side=BUY \
  --data type=LIMIT \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BTCUSD_200925",
  "side": "BUY",
  "type": "LIMIT",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "clientOrderId": "testOrder",
  "cumQty": "0",
  "executedQty": "0",
  "orderId": 22542179,
  "origQty": "10",
  "price": "0",
  "reduceOnly": false,
  "closePosition": false,
  "side": "SELL",
  "positionSide": "SHORT",
  "status": "NEW",
  "stopPrice": "0",
  "symbol": "BTCUSD_200925",
  "pair": "BTCUSD",
  "timeInForce": "GTC",
  "type": "TRAILING_STOP_MARKET",
  "origType": "TRAILING_STOP_MARKET",
  "activatePrice": "9020",
  "priceRate": "0.3",
  "updateTime": 1566818724722,
  "workingType": "CONTRACT_PRICE",
  "priceProtect": false,
  "priceMatch": "NONE",
  "selfTradePreventionMode": "NONE"
}

json

application/json

Cancel Order (TRADE)

Cancel an active order.

DELETE

/dapi/v1/order

https://dapi.binance.com

Cancel Order (TRADE) › 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

Cancel Order (TRADE) › 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

Cancel Order (TRADE) › 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

Cancel Order (TRADE) › Query Parameters

symbol

string · required

Symbol

Example: BTCUSD_200925

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

orderId

integer · int64

Order ID

Example: 283194212

origClientOrderId

string

Client order ID

Example: myOrder1

recvWindow

integer · int64 · max: 60000

Example: 5000

Cancel Order (TRADE) › Responses

200

Cancel Order

clientOrderId

string

Client order ID.

Example: myOrder1

cumQty

string

Cumulative filled quantity.

Example: 0

executedQty

string

Executed quantity

Example: 0

orderId

integer · int64

Sub-order ID

Example: 283194212

origQty

string

Original order quantity

Example: 11

price

string

Latest token price.

Example: 0

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

side

string

Trading side

Example: BUY

positionSide

string

Position side

Example: SHORT

status

string

Enum：completed，processing

Example: CANCELED

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 9300

closePosition

boolean

if Close-All

Example: false

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

timeInForce

string

Time in force

Example: GTC

origType

string

Original order type.

Example: TRAILING_STOP_MARKET

type

string

Order type.

Example: TRAILING_STOP_MARKET

activatePrice

string

activation price, only return with TRAILING_STOP_MARKET order

Example: 9020

priceRate

string

callback rate, only return with TRAILING_STOP_MARKET order

Example: 0.3

updateTime

integer · int64

update time

Example: 1571110484038

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

DELETE/dapi/v1/order

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

Example Responses

{
  "clientOrderId": "myOrder1",
  "cumQty": "0",
  "executedQty": "0",
  "orderId": 283194212,
  "origQty": "11",
  "price": "0",
  "reduceOnly": false,
  "side": "BUY",
  "positionSide": "SHORT",
  "status": "CANCELED",
  "stopPrice": "9300",
  "closePosition": false,
  "symbol": "BTCUSD_200925",
  "pair": "BTCUSD",
  "timeInForce": "GTC",
  "origType": "TRAILING_STOP_MARKET",
  "type": "TRAILING_STOP_MARKET",
  "activatePrice": "9020",
  "priceRate": "0.3",
  "updateTime": 1571110484038,
  "workingType": "CONTRACT_PRICE",
  "priceProtect": false,
  "priceMatch": "NONE",
  "selfTradePreventionMode": "NONE"
}

json

application/json

Change Initial Leverage (TRADE)

Change user's initial leverage in the specific symbol market.

For Hedge Mode, LONG and SHORT positions of one symbol use the same initial leverage and share a total notional value.

POST

/dapi/v1/leverage

https://dapi.binance.com

Change Initial Leverage (TRADE) › 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

Change Initial Leverage (TRADE) › 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

Change Initial Leverage (TRADE) › 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

Change Initial Leverage (TRADE) › Request Body

symbol

string · required

Symbol

Example: BTCUSD_200925

leverage

integer · int64 · required

target initial leverage: int from 1 to 125

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

Change Initial Leverage (TRADE) › Responses

200

Change Initial Leverage

leverage

integer · int64

Leverage value.

Example: 21

maxQty

string

maximum quantity of base asset

Example: 1000

symbol

string

Trading symbol

Example: BTCUSD_200925

Change Margin Type (TRADE)

Change user's margin type in the specific symbol market.For Hedge Mode, LONG and SHORT positions of one symbol use the same margin type.

With ISOLATED margin type, margins of the LONG and SHORT positions are isolated from each other.

POST

/dapi/v1/marginType

https://dapi.binance.com

Change Margin Type (TRADE) › 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

Change Margin Type (TRADE) › 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

Change Margin Type (TRADE) › 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

Change Margin Type (TRADE) › Request Body

symbol

string · required

Symbol

Example: BTCUSD_200925

marginType

string · enum · required

Enum values:

ISOLATED

CROSSED

Example: ISOLATED

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

Change Margin Type (TRADE) › Responses

200

Change Margin Type

code

integer · int64

API response code. "000000" indicates success.

Example: 200

msg

string

Message details.

Example: success

Current All Open Orders (USER_DATA)

Get all open orders on a symbol. Careful when accessing this with no symbol.

GET

/dapi/v1/openOrders

https://dapi.binance.com

Current All Open Orders (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

Current All Open Orders (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 for a single symbol, 40 for mutltiple symbols

Current All Open Orders (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

Current All Open Orders (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. After CM migration, an invalid symbol returns -1121 (previously a silent 200).

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

recvWindow

integer · int64 · max: 60000

Example: 5000

Current All Open Orders (USER_DATA) › Responses

200

Current All Open Orders

object

avgPrice

string

Average execution price

Example: 0.0

clientOrderId

string

Client order ID.

Example: abc

cumBase

string

Cumulative base asset amount.

Example: 0

executedQty

string

Executed quantity

Example: 0

orderId

integer · int64

Sub-order ID

Example: 1917641

origQty

string

Original order quantity

Example: 0.40

origType

string

Original order type.

Example: TRAILING_STOP_MARKET

price

string

Latest token price.

Example: 0

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

side

string

Trading side

Example: BUY

positionSide

string

Position side

Example: SHORT

status

string

Enum：completed，processing

Example: NEW

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 9300

closePosition

boolean

if Close-All

Example: false

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

time

integer · int64

Time

Example: 1579276756075

timeInForce

string

Time in force

Example: GTC

type

string

Order type.

Example: TRAILING_STOP_MARKET

activatePrice

string

activation price, only return with TRAILING_STOP_MARKET order

Example: 9020

priceRate

string

callback rate, only return with TRAILING_STOP_MARKET order

Example: 0.3

updateTime

integer · int64

update time

Example: 1579276756075

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

GET/dapi/v1/openOrders

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

Example Responses

[
  {
    "avgPrice": "0.0",
    "clientOrderId": "abc",
    "cumBase": "0",
    "executedQty": "0",
    "orderId": 1917641,
    "origQty": "0.40",
    "origType": "TRAILING_STOP_MARKET",
    "price": "0",
    "reduceOnly": false,
    "side": "BUY",
    "positionSide": "SHORT",
    "status": "NEW",
    "stopPrice": "9300",
    "closePosition": false,
    "symbol": "BTCUSD_200925",
    "pair": "BTCUSD",
    "time": 1579276756075,
    "timeInForce": "GTC",
    "type": "TRAILING_STOP_MARKET",
    "activatePrice": "9020",
    "priceRate": "0.3",
    "updateTime": 1579276756075,
    "workingType": "CONTRACT_PRICE",
    "priceProtect": false,
    "priceMatch": "NONE",
    "selfTradePreventionMode": "NONE"
  }
]

json

application/json

Get Order Modify History (USER_DATA)

Get order modification history

GET

/dapi/v1/orderAmendment

https://dapi.binance.com

Get Order Modify 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 Order Modify 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 Weight1

Get Order Modify 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 Order Modify History (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

orderId

integer · int64

Order ID

Example: 20072994037

origClientOrderId

string

Client order ID

Example: LJ9R4QZDihCaS8UAOOLpgW

startTime

integer · int64

Timestamp in ms to get modification history from INCLUSIVE

Example: 1623319461670

endTime

integer · int64

Timestamp in ms to get modification history until INCLUSIVE

Example: 1641782889000

limit

integer · int64 · max: 100

Maximum number of records to return.

Example: 30

Default: 50

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Order Modify History (USER_DATA) › Responses

200

Get Order Modify History

object

amendmentId

integer · int64

Order modification ID

Example: 5363

symbol

string

Trading symbol

Example: BTCUSD_PERP

pair

string

Pair

Example: BTCUSD

orderId

integer · int64

Sub-order ID

Example: 20072994037

clientOrderId

string

Client order ID.

Example: LJ9R4QZDihCaS8UAOOLpgW

time

integer · int64

Time

Example: 1629184560899

object

Order amendment details.

object

Latest token price.

before

string

Before value.

Example: 30004

after

string

After value.

Example: 30003.2

object

Original order quantity

before

string

Before value.

Example: 1

after

string

After value.

Example: 1

count

integer · int64

Total number of trades in the 24h window.

Example: 3

Get Position Margin Change History (TRADE)

Get position margin change history

GET

/dapi/v1/positionMargin/history

https://dapi.binance.com

Get Position Margin Change History (TRADE) › 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 Position Margin Change History (TRADE) › 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 Position Margin Change History (TRADE) › 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 Position Margin Change History (TRADE) › Query Parameters

symbol

string · required

Example: BTCUSD

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

type

integer · int64

1: Add position margin,2: Reduce position margin

Example: 1

startTime

integer · int64

Start time

Example: 1623319461670

endTime

integer · int64

End time

Example: 1641782889000

limit

integer · int64

Maximum number of records to return.

Example: 30

Default: 50

recvWindow

integer · int64 · max: 60000

Example: 5000

Get Position Margin Change History (TRADE) › Responses

200

Get Position Margin Change History

object

amount

string

Amount.

Example: 23.36332311

asset

string

asset name

Example: BTC

symbol

string

Trading symbol

Example: BTCUSD_200925

time

integer · int64

Time

Example: 1578047897183

type

integer · int64

Order type.

Example: 1

positionSide

string

Position side

Example: BOTH

Modify Isolated Position Margin (TRADE)

Modify Isolated Position Margin

POST

/dapi/v1/positionMargin

https://dapi.binance.com

Modify Isolated Position Margin (TRADE) › 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

Modify Isolated Position Margin (TRADE) › 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

Modify Isolated Position Margin (TRADE) › 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

Modify Isolated Position Margin (TRADE) › Request Body

symbol

string · required

Symbol

Example: BTCUSDT

amount

number · float · required

Margin asset

Example: 1.0

type

integer · int64 · required

1: Add position margin,2: Reduce position margin

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

positionSide

string · enum

Default BOTH for One-way Mode ; LONG or SHORT for Hedge Mode. It must be sent with Hedge Mode.

Enum values:

BOTH

LONG

SHORT

Example: BOTH

recvWindow

integer · int64 · max: 60000

Example: 5000

Modify Isolated Position Margin (TRADE) › Responses

200

Modify Isolated Position Margin

amount

number · float

Amount.

Example: 100

code

integer · int64

API response code. "000000" indicates success.

Example: 200

msg

string

Message details.

Example: Successfully modify position margin.

type

integer · int64

Order type.

Example: 1

Position ADL Quantile Estimation (USER_DATA)

Query position ADL quantile estimation

Values update every 30s.
Values 0, 1, 2, 3, 4 shows the queue position and possibility of ADL from low to high.
For positions of the symbol are in One-way Mode or isolated margined in Hedge Mode, "LONG", "SHORT", and "BOTH" will be returned to show the positions' adl quantiles of different position sides.
If the positions of the symbol are crossed margined in Hedge Mode:
- "HEDGE" as a sign will be returned instead of "BOTH";
- A same value caculated on unrealized pnls on long and short sides' positions will be shown for "LONG" and "SHORT" when there are positions in both of long and short sides.

GET

/dapi/v1/adlQuantile

https://dapi.binance.com

Position ADL Quantile Estimation (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

Position ADL Quantile Estimation (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

Position ADL Quantile Estimation (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

Position ADL Quantile Estimation (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_200925

recvWindow

integer · int64 · max: 60000

Example: 5000

Position ADL Quantile Estimation (USER_DATA) › Responses

200

Position ADL Quantile Estimation

object

symbol

string

Trading symbol

Example: BTCUSD_200925

object

ADL quantile information.

LONG

integer · int64

adl quantile for "LONG" position in hedge mode

Example: 3

SHORT

integer · int64

adl qauntile for "SHORT" position in hedge mode

Example: 3

HEDGE

integer · int64

Hedge mode ADL quantile.

Example: 0

BOTH

integer · int64

One-way mode ADL quantile.

Example: 0

Position Information (USER_DATA)

Get current account information.

GET

/dapi/v1/positionRisk

https://dapi.binance.com

Position 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

Position 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 Weight1

Position 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

Position 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

marginAsset

string

Example: USDT

pair

string

Example: BTCUSDT

recvWindow

integer · int64 · max: 60000

Example: 5000

Position Information (USER_DATA) › Responses

200

Position Information

object

symbol

string

Trading symbol

Example: BTCUSD_201225

positionAmt

string

position amount

Example: 0

entryPrice

string

Position entry price.

Example: 0.0

breakEvenPrice

string

break-even price

Example: 0.0

markPrice

string

mark price

Example: 0.00000000

unRealizedProfit

string

Unrealized profit.

Example: 0.00000000

liquidationPrice

string

Liquidation price.

Example: 0

leverage

string

Leverage value.

Example: 125

maxQty

string

maximum quantity of base asset

Example: 50

marginType

string

Margin type.

Example: cross

isolatedMargin

string

Isolated margin amount.

Example: 0.00000000

isAutoAddMargin

string

Whether auto-add margin is enabled.

Example: false

positionSide

string

Position side

Example: BOTH

updateTime

integer · int64

update time

Example: 0

Query Current Open Order (USER_DATA)

Query Current Open Order

GET

/dapi/v1/openOrder

https://dapi.binance.com

Query Current Open Order (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 Current Open Order (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 Current Open Order (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 Current Open Order (USER_DATA) › Query Parameters

symbol

string · required

Symbol

Example: BTCUSD_200925

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

orderId

integer · int64

Order ID

Example: 1

origClientOrderId

string

Client order ID

Example: 1

recvWindow

integer · int64 · max: 60000

Example: 5000

Query Current Open Order (USER_DATA) › Responses

200

Current Open Order

avgPrice

string

Average execution price

Example: 0.0

clientOrderId

string

Client order ID.

Example: abc

cumBase

string

Cumulative base asset amount.

Example: 0

executedQty

string

Executed quantity

Example: 0

orderId

integer · int64

Sub-order ID

Example: 1917641

origQty

string

Original order quantity

Example: 0.40

origType

string

Original order type.

Example: TRAILING_STOP_MARKET

price

string

Latest token price.

Example: 0

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

side

string

Trading side

Example: BUY

positionSide

string

Position side

Example: SHORT

status

string

Enum：completed，processing

Example: NEW

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 9300

closePosition

boolean

if Close-All

Example: false

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

time

integer · int64

Time

Example: 1579276756075

timeInForce

string

Time in force

Example: GTC

type

string

Order type.

Example: TRAILING_STOP_MARKET

activatePrice

string

activation price, only return with TRAILING_STOP_MARKET order

Example: 9020

priceRate

string

callback rate, only return with TRAILING_STOP_MARKET order

Example: 0.3

updateTime

integer · int64

update time

Example: 1579276756075

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

priceMatch

string

price match mode

Example: NONE

selfTradePreventionMode

string

self trading preventation mode

Example: NONE

GET/dapi/v1/openOrder

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

Example Responses

{
  "avgPrice": "0.0",
  "clientOrderId": "abc",
  "cumBase": "0",
  "executedQty": "0",
  "orderId": 1917641,
  "origQty": "0.40",
  "origType": "TRAILING_STOP_MARKET",
  "price": "0",
  "reduceOnly": false,
  "side": "BUY",
  "positionSide": "SHORT",
  "status": "NEW",
  "stopPrice": "9300",
  "closePosition": false,
  "symbol": "BTCUSD_200925",
  "pair": "BTCUSD",
  "time": 1579276756075,
  "timeInForce": "GTC",
  "type": "TRAILING_STOP_MARKET",
  "activatePrice": "9020",
  "priceRate": "0.3",
  "updateTime": 1579276756075,
  "workingType": "CONTRACT_PRICE",
  "priceProtect": false,
  "priceMatch": "NONE",
  "selfTradePreventionMode": "NONE"
}

json

application/json

User's Force Orders (USER_DATA)

User's Force Orders

GET

/dapi/v1/forceOrders

https://dapi.binance.com

User's Force Orders (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's Force Orders (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

20 (after CM migration: 20 with symbol / 50 without symbol)

User's Force Orders (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's Force Orders (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_200925

autoCloseType

string · enum

Enum values:

LIQUIDATION

ADL

Example: LIQUIDATION

startTime

integer · int64

Example: 1623319461670

endTime

integer · int64

Example: 1641782889000

limit

integer · int64 · max: 100

Maximum number of records to return.

Example: 30

Default: 50

recvWindow

integer · int64 · max: 60000

Example: 5000

User's Force Orders (USER_DATA) › Responses

200

User's Force Orders

object

orderId

integer · int64

Sub-order ID

Example: 165123080

symbol

string

Trading symbol

Example: BTCUSD_200925

pair

string

Pair

Example: BTCUSD

status

string

Enum：completed，processing

Example: FILLED

clientOrderId

string

Client order ID.

Example: autoclose-1596542005017000006

price

string

Latest token price.

Example: 11326.9

avgPrice

string

Average execution price

Example: 11326.9

origQty

string

Original order quantity

Example: 1

executedQty

string

Executed quantity

Example: 1

cumBase

string

Cumulative base asset amount.

Example: 0.00882854

timeInForce

string

Time in force

Example: IOC

type

string

Order type.

Example: LIMIT

reduceOnly

boolean

Whether the order is reduce-only.

Example: false

closePosition

boolean

if Close-All

Example: false

side

string

Trading side

Example: SELL

positionSide

string

Position side

Example: BOTH

stopPrice

string

please ignore when order type is TRAILING_STOP_MARKET

Example: 0

workingType

string

Stop trigger price type.

Example: CONTRACT_PRICE

priceProtect

boolean

if conditional order trigger is protected

Example: false

origType

string

Original order type.

Example: LIMIT

time

integer · int64

Time

Example: 1596542005019

updateTime

integer · int64

update time

Example: 1596542005050

GET/dapi/v1/forceOrders

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

Example Responses

[
  {
    "orderId": 165123080,
    "symbol": "BTCUSD_200925",
    "pair": "BTCUSD",
    "status": "FILLED",
    "clientOrderId": "autoclose-1596542005017000006",
    "price": "11326.9",
    "avgPrice": "11326.9",
    "origQty": "1",
    "executedQty": "1",
    "cumBase": "0.00882854",
    "timeInForce": "IOC",
    "type": "LIMIT",
    "reduceOnly": false,
    "closePosition": false,
    "side": "SELL",
    "positionSide": "BOTH",
    "stopPrice": "0",
    "workingType": "CONTRACT_PRICE",
    "priceProtect": false,
    "origType": "LIMIT",
    "time": 1596542005019,
    "updateTime": 1596542005050
  }
]

json

application/json