Trade

Endpoint

Cancel All Open Orders on a Symbol

Cancels all active orders on a symbol. This includes orders that are part of an order list.

DELETE

/api/v3/openOrders

https://api.binance.com

Cancel All Open Orders on a Symbol › 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 on a Symbol › 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 on a Symbol › 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 on a Symbol › Query Parameters

symbol

string · required

Example: BNBUSDT

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

number · float · max: 60000

Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Cancel All Open Orders on a Symbol › Responses

200

Cancel All Open Orders on a Symbol

object

symbol

string

Example: BTCUSDT

origClientOrderId

string

Example: E6APeyTJvkMvLMYMqu1KQ4

orderId

integer · int64

Example: 11

orderListId

integer · int64

Example: -1

clientOrderId

string

Example: pXLV6Hz6mprAcVYpVMTGgx

transactTime

integer · int64

Example: 1684804350068

price

string

Example: 0.089853

origQty

string

Example: 0.178622

executedQty

string

Example: 0.000000

origQuoteOrderQty

string

Example: 0.000000

cummulativeQuoteQty

string

Example: 0.000000

status

string

Example: CANCELED

timeInForce

string

Example: GTC

type

string

Example: LIMIT

side

string

Example: BUY

selfTradePreventionMode

string

Example: NONE

New order

Send in a new order.

This adds 1 order to the EXCHANGE_MAX_ORDERS filter and the MAX_NUM_ORDERS filter.

POST

/api/v3/order

https://api.binance.com

Unfilled Order Count1

New order › 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 › 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

New order › 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 › Request Body

symbol

string · required

Example: BNBUSDT

side

string · enum · required

Please see Enums for supported values.

Enum values:

BUY

SELL

Example: BUY

type

string · enum · required

Please see Enums for supported values.

Enum values:

MARKET

LIMIT

STOP_LOSS

STOP_LOSS_LIMIT

TAKE_PROFIT

TAKE_PROFIT_LIMIT

LIMIT_MAKER

Example: MARKET

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

timeInForce

string · enum

Please see Enums for supported values.

Enum values:

GTC

IOC

FOK

Example: GTC

quantity

number · float

Example: 1

quoteOrderQty

number · float

Example: 1

price

number · float

Example: 400

newClientOrderId

string

A unique id among open orders. Automatically generated if not sent.
Orders with the same newClientOrderID can be accepted only when the previous one is filled, otherwise the order will be rejected.

Example: myOrder1

strategyId

integer · int64

Example: 1

strategyType

integer · min: 1000000

The value cannot be less than 1000000.

Example: 1

stopPrice

number · float

Used with STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, and TAKE_PROFIT_LIMIT orders.

Example: 1

trailingDelta

integer · int64

See Trailing Stop order FAQ

Example: 1

icebergQty

number · float

Used with LIMIT, STOP_LOSS_LIMIT, and TAKE_PROFIT_LIMIT to create an iceberg order.

Example: 1

newOrderRespType

string · enum

MARKET and LIMIT order types default to FULL, all other orders default to ACK.

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol.

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

pegPriceType

string · enum

See Pegged Orders Info

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pegOffsetValue

integer · max: 100

Price level to peg the price to (max: 100). See Pegged Orders Info

Example: 1

pegOffsetType

string · enum

Only PRICE_LEVEL is supported. See Pegged Orders Info

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

recvWindow

number · float · max: 60000

Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Data Source: Matching Engine

Some additional mandatory parameters based on order type:

Type	Additional mandatory parameters	Additional Information
`LIMIT`	`timeInForce`, `quantity`, `price`
`MARKET`	`quantity` or `quoteOrderQty`	`MARKET` orders using the `quantity` field specifies the amount of the `base asset` the user wants to buy or sell at the market price. E.g. MARKET order on BTCUSDT will specify how much BTC the user is buying or selling. `MARKET` orders using `quoteOrderQty` specifies the amount the user wants to spend (when buying) or receive (when selling) the `quote` asset; the correct `quantity` will be determined based on the market liquidity and `quoteOrderQty`. E.g. Using the symbol BTCUSDT: `BUY` side, the order will buy as many BTC as `quoteOrderQty` USDT can. `SELL` side, the order will sell as much BTC needed to receive `quoteOrderQty` USDT.
`STOP_LOSS`	`quantity`, `stopPrice` or `trailingDelta`	This will execute a `MARKET` order when the conditions are met. (e.g. `stopPrice` is met or `trailingDelta` is activated)
`STOP_LOSS_LIMIT`	`timeInForce`, `quantity`, `price`, `stopPrice` or `trailingDelta`
`TAKE_PROFIT`	`quantity`, `stopPrice` or `trailingDelta`	This will execute a `MARKET` order when the conditions are met. (e.g. `stopPrice` is met or `trailingDelta` is activated)
`TAKE_PROFIT_LIMIT`	`timeInForce`, `quantity`, `price`, `stopPrice` or `trailingDelta`
`LIMIT_MAKER`	`quantity`, `price`	This is a `LIMIT` order that will be rejected if the order immediately matches and trades as a taker. This is also known as a POST-ONLY order.

Notes on using parameters for Pegged Orders:

These parameters are allowed for LIMIT, LIMIT_MAKER, STOP_LOSS_LIMIT, TAKE_PROFIT_LIMIT orders.
If pegPriceType is specified, price becomes optional. Otherwise, it is still mandatory.
pegPriceType=PRIMARY_PEG means the primary peg, that is the best price on the same side of the order book as your order.
pegPriceType=MARKET_PEG means the market peg, that is the best price on the opposite side of the order book from your order.
Use pegOffsetType and pegOffsetValue to request a price level other than the best one. These parameters must be specified together.

Other info:

Any LIMIT or LIMIT_MAKER type order can be made an iceberg order by sending an icebergQty.
Any order with an icebergQty MUST have timeInForce set to GTC.
For STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT_LIMIT and TAKE_PROFIT orders, trailingDelta can be combined with stopPrice.
MARKET orders using quoteOrderQty will not break LOT_SIZE filter rules; the order will execute a quantity that will have the notional value as close as possible to quoteOrderQty. Trigger order price rules against market price for both MARKET and LIMIT versions:
- Price above market price: STOP_LOSS BUY, TAKE_PROFIT SELL
- Price below market price: STOP_LOSS SELL, TAKE_PROFIT BUY

New order › Responses

200

New order

symbol

string

Example: BTCUSDT

orderId

integer · int64

Example: 28

orderListId

integer · int64

Unless it's part of an order list, value will be -1

Example: -1

clientOrderId

string

Example: 6gCrw2kRUAF9CvJDGP16IP

transactTime

integer · int64

Example: 1507725176595

price

string

Example: 1

origQty

string

Example: 10

executedQty

string

Example: 10

origQuoteOrderQty

string

Example: 0

cummulativeQuoteQty

string

Example: 10

status

string

Example: FILLED

timeInForce

string

Example: GTC

type

string

Example: MARKET

side

string

Example: SELL

workingTime

integer · int64

Example: 1507725176595

selfTradePreventionMode

string

Example: NONE

object[]

POST/api/v3/order

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

Example Request Body

{
  "symbol": "BNBUSDT",
  "side": "BUY",
  "type": "MARKET",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "symbol": "BTCUSDT",
  "orderId": 28,
  "orderListId": -1,
  "clientOrderId": "6gCrw2kRUAF9CvJDGP16IP",
  "transactTime": 1507725176595,
  "price": 1,
  "origQty": 10,
  "executedQty": 10,
  "origQuoteOrderQty": 0,
  "cummulativeQuoteQty": 10,
  "status": "FILLED",
  "timeInForce": "GTC",
  "type": "MARKET",
  "side": "SELL",
  "workingTime": 1507725176595,
  "selfTradePreventionMode": "NONE",
  "fills": [
    {
      "price": 4000,
      "qty": 1,
      "commission": 4,
      "commissionAsset": "USDT",
      "tradeId": 56
    }
  ]
}

json

application/json

Cancel order

Cancel an active order.

DELETE

/api/v3/order

https://api.binance.com

Cancel order › 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 › 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 › 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 › Query Parameters

symbol

string · required

Example: BNBUSDT

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

Example: 1

origClientOrderId

string

Example: myOrder1

newClientOrderId

string

Used to uniquely identify this cancel. Automatically generated by default.

Example: cancelMyOrder1

cancelRestrictions

string · enum

Supported values:
ONLY_NEW - Cancel will succeed if the order status is NEW.
ONLY_PARTIALLY_FILLED - Cancel will succeed if order status is PARTIALLY_FILLED.

Enum values:

ONLY_NEW

ONLY_PARTIALLY_FILLED

Example: ONLY_NEW

recvWindow

number · float · max: 60000

Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Cancel order › Responses

200

Cancel order

symbol

string

Example: LTCBTC

orderId

integer · int64

Example: 4

orderListId

integer · int64

Unless it's part of an order list, value will be -1

Example: -1

origClientOrderId

string

Example: myOrder1

clientOrderId

string

Example: cancelMyOrder1

transactTime

integer · int64

Example: 1684804350068

price

string

Example: 2.00000000

origQty

string

Example: 1.00000000

executedQty

string

Example: 0.00000000

origQuoteOrderQty

string

Example: 0.000000

cummulativeQuoteQty

string

Example: 0.00000000

status

string

Example: CANCELED

timeInForce

string

Example: GTC

type

string

Example: LIMIT

side

string

Example: BUY

selfTradePreventionMode

string

Example: NONE

icebergQty

string

Quantity for the iceberg order. Appears only if the parameter icebergQty was sent in the request.

Example: 0.00000000

preventedMatchId

integer · int64

When used together with symbol, can be used to query a prevented match. Appears only if the order expired due to STP.

Example: 0

preventedQuantity

string

Order quantity that expired due to STP. Appears only if the order expired due to STP.

Example: 1.200000

stopPrice

string

Price when the algorithmic order will be triggered. Appears for STOP_LOSS, TAKE_PROFIT, STOP_LOSS_LIMIT, and TAKE_PROFIT_LIMIT orders.

Example: 23500.00000000

strategyId

integer · int64

Can be used to label an order that's part of an order strategy. Appears if the parameter was populated in the request.

Example: 37463720

strategyType

integer · int64

Can be used to label an order that is using an order strategy. Appears if the parameter was populated in the request.

Example: 1000000

trailingDelta

integer · int64

Delta price change required before order activation. Appears for trailing stop orders.

Example: 10

trailingTime

integer · int64

Time when the trailing order becomes active and starts tracking price changes. Appears only for trailing stop orders.

Example: -1

usedSor

boolean

Indicates whether the order used SOR. Appears when placing orders using SOR.

Example: true

workingFloor

string

Indicates whether the order is being filled by SOR or by the order book to which it was submitted. Appears when placing orders using SOR.

Example: SOR

pegPriceType

string

Price peg type. Only for pegged orders.

Example: PRIMARY_PEG

pegOffsetType

string

Price peg offset type. Only for pegged orders, if requested.

Example: PRICE_LEVEL

pegOffsetValue

integer · int64

Price peg offset value. Only for pegged orders, if requested.

Example: 5

peggedPrice

string

Current price the order is pegged at. Only for pegged orders, once determined.

Example: 87523.83710000

expiryReason

string

Cause of the order's expiration. Returned when an order has expired.

Example: INSUFFICIENT_LIQUIDITY

DELETE/api/v3/order

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

Example Responses

{
  "symbol": "LTCBTC",
  "orderId": 4,
  "orderListId": -1,
  "origClientOrderId": "myOrder1",
  "clientOrderId": "cancelMyOrder1",
  "transactTime": 1684804350068,
  "price": "2.00000000",
  "origQty": "1.00000000",
  "executedQty": "0.00000000",
  "origQuoteOrderQty": "0.000000",
  "cummulativeQuoteQty": "0.00000000",
  "status": "CANCELED",
  "timeInForce": "GTC",
  "type": "LIMIT",
  "side": "BUY",
  "selfTradePreventionMode": "NONE",
  "icebergQty": "0.00000000",
  "preventedMatchId": 0,
  "preventedQuantity": "1.200000",
  "stopPrice": "23500.00000000",
  "strategyId": 37463720,
  "strategyType": 1000000,
  "trailingDelta": 10,
  "trailingTime": -1,
  "usedSor": true,
  "workingFloor": "SOR",
  "pegPriceType": "PRIMARY_PEG",
  "pegOffsetType": "PRICE_LEVEL",
  "pegOffsetValue": 5,
  "peggedPrice": "87523.83710000",
  "expiryReason": "INSUFFICIENT_LIQUIDITY"
}

json

application/json

Cancel Order list

Cancel an entire Order list

DELETE

/api/v3/orderList

https://api.binance.com

Cancel Order list › 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 list › 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 list › 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 list › Query Parameters

symbol

string · required

Example: BNBUSDT

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

orderListId

integer · int64

Either orderListId or listClientOrderId must be provided

Example: 1

listClientOrderId

string

Either orderListId or listClientOrderId must be provided

Example: C3wyj4WVEktd7u9aVBRXcN

newClientOrderId

string

Used to uniquely identify this cancel. Automatically generated by default.

Example: cancelMyOrder1

recvWindow

number · float · max: 60000

Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Cancel Order list › Responses

200

Cancel Order list

orderListId

integer · int64

Example: 0

contingencyType

string

Example: OCO

listStatusType

string

Example: ALL_DONE

listOrderStatus

string

Example: ALL_DONE

listClientOrderId

string

Example: C3wyj4WVEktd7u9aVBRXcN

transactionTime

integer · int64

Example: 1574040868128

symbol

string

Example: LTCBTC

object[]

DELETE/api/v3/orderList

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

Example Responses

{
  "orderListId": 0,
  "contingencyType": "OCO",
  "listStatusType": "ALL_DONE",
  "listOrderStatus": "ALL_DONE",
  "listClientOrderId": "C3wyj4WVEktd7u9aVBRXcN",
  "transactionTime": 1574040868128,
  "symbol": "LTCBTC",
  "orders": [
    {
      "symbol": "LTCBTC",
      "orderId": 2,
      "clientOrderId": "pO9ufTiFGg3nw2fOdgeOXa"
    }
  ],
  "orderReports": [
    {
      "symbol": "LTCBTC",
      "origClientOrderId": "pO9ufTiFGg3nw2fOdgeOXa",
      "orderId": 2,
      "orderListId": 0,
      "clientOrderId": "unfWT8ig8i0uj6lPuYLez6",
      "transactTime": 1688005070874,
      "price": "1.00000000",
      "origQty": "10.00000000",
      "executedQty": "0.00000000",
      "origQuoteOrderQty": "0.000000",
      "cummulativeQuoteQty": "0.00000000",
      "status": "CANCELED",
      "timeInForce": "GTC",
      "type": "STOP_LOSS_LIMIT",
      "side": "SELL",
      "icebergQty": "0.00000000",
      "preventedMatchId": 0,
      "preventedQuantity": "1.200000",
      "stopPrice": "0.00000000",
      "strategyId": 1,
      "strategyType": 1000000,
      "trailingDelta": 10,
      "trailingTime": -1,
      "usedSor": true,
      "workingFloor": "SOR",
      "pegPriceType": "PRIMARY_PEG",
      "pegOffsetType": "PRICE_LEVEL",
      "pegOffsetValue": 5,
      "peggedPrice": "87523.83710000",
      "expiryReason": "INSUFFICIENT_LIQUIDITY"
    }
  ]
}

json

application/json

Order Amend Keep Priority

Reduce the quantity of an existing open order.

This adds 0 orders to the EXCHANGE_MAX_ORDERS filter and the MAX_NUM_ORDERS filter.

Read Order Amend Keep Priority FAQ to learn more.

PUT

/api/v3/order/amend/keepPriority

https://api.binance.com

Unfilled Order Count0

Order Amend Keep Priority › 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

Order Amend Keep Priority › 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 Weight4

Order Amend Keep Priority › 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

Order Amend Keep Priority › Request Body

symbol

string · required

Example: BNBUSDT

newQty

number · float · required

newQty must be greater than 0 and less than the order's quantity.

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

orderId

integer · int64

orderId or origClientOrderId must be sent

Example: 1

origClientOrderId

string

orderId or origClientOrderId must be sent

Example: myOrder1

newClientOrderId

string

The new client order ID for the order after being amended.
If not sent, one will be randomly generated.
It is possible to reuse the current clientOrderId by sending it as the newClientOrderId.

Example: myOrder2

recvWindow

number · float

The value cannot be greater than 60000.
Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Order Amend Keep Priority › Responses

200

Order Amend Keep Priority

transactTime

integer · int64

Example: 1741926410255

executionId

integer · int64

Example: 75

object

PUT/api/v3/order/amend/keepPriority

curl --request PUT \
  --url https://api.binance.com/api/v3/order/amend/keepPriority \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data newQty=1 \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "newQty": 1,
  "timestamp": 1770736694138
}

json

Example Responses

{
  "transactTime": 1741926410255,
  "executionId": 75,
  "amendedOrder": {
    "symbol": "BTCUSDT",
    "orderId": 33,
    "orderListId": -1,
    "origClientOrderId": "5xrgbMyg6z36NzBn2pbT8H",
    "clientOrderId": "PFaq6hIHxqFENGfdtn4J6Q",
    "price": "6.00000000",
    "qty": "5.00000000",
    "executedQty": "0.00000000",
    "preventedQty": "0.00000000",
    "quoteOrderQty": "0.00000000",
    "cumulativeQuoteQty": "0.00000000",
    "status": "NEW",
    "timeInForce": "GTC",
    "type": "LIMIT",
    "side": "SELL",
    "workingTime": 1741926410242,
    "selfTradePreventionMode": "NONE",
    "icebergQty": "0.00000000",
    "preventedMatchId": 0,
    "preventedQuantity": "1.200000",
    "stopPrice": "0.00000000",
    "strategyId": 1,
    "strategyType": 1000000,
    "trailingDelta": 10,
    "trailingTime": -1,
    "usedSor": true,
    "workingFloor": "SOR",
    "pegPriceType": "PRIMARY_PEG",
    "pegOffsetType": "PRICE_LEVEL",
    "pegOffsetValue": 5,
    "peggedPrice": "87523.83710000",
    "expiryReason": "INSUFFICIENT_LIQUIDITY"
  },
  "listStatus": {
    "orderListId": 1,
    "contingencyType": "OTO",
    "listOrderStatus": "EXECUTING",
    "listClientOrderId": "AT7FTxZXylVSwRoZs52mt3",
    "symbol": "BTCUSDT",
    "orders": [
      {
        "symbol": "BTCUSDT",
        "orderId": 8,
        "clientOrderId": "GkwwHZUUbFtZOoH1YsZk9Q"
      }
    ]
  }
}

json

application/json

Cancel an Existing Order and Send a New Order

Cancels an existing order and places a new order on the same symbol.
Filters and Order Count are evaluated before the processing of the cancellation and order placement occurs.
A new order that was not attempted (i.e. when newOrderResult: NOT_ATTEMPTED), will still increase the unfilled order count by 1.
You can only cancel an individual order from an orderList using this endpoint, but the result is the same as canceling the entire orderList.

POST

/api/v3/order/cancelReplace

https://api.binance.com

Unfilled Order Count1

Cancel an Existing Order and Send a New Order › 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 an Existing Order and Send a New Order › 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 an Existing Order and Send a New Order › 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 an Existing Order and Send a New Order › Request Body

symbol

string · required

Example: BNBUSDT

side

string · enum · required

Enum values:

BUY

SELL

Example: BUY

type

string · enum · required

Enum values:

MARKET

LIMIT

STOP_LOSS

STOP_LOSS_LIMIT

TAKE_PROFIT

TAKE_PROFIT_LIMIT

LIMIT_MAKER

Example: MARKET

cancelReplaceMode

string · enum · required

The allowed values are:
STOP_ON_FAILURE - If the cancel request fails, the new order placement will not be attempted.
ALLOW_FAILURE - new order placement will be attempted even if cancel request fails.

Enum values:

STOP_ON_FAILURE

ALLOW_FAILURE

Example: STOP_ON_FAILURE

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

timeInForce

string · enum

Enum values:

GTC

IOC

FOK

Example: GTC

quantity

number · float

Example: 1

quoteOrderQty

number · float

Example: 1

price

number · float

Example: 400

cancelNewClientOrderId

string

Used to uniquely identify this cancel. Automatically generated by default.

Example: cancelMyOrder1

cancelOrigClientOrderId

string

Either cancelOrderId or cancelOrigClientOrderId must be sent.

If both cancelOrderId and cancelOrigClientOrderId parameters are provided, the cancelOrderId is searched first, then the cancelOrigClientOrderId from that result is checked against that order.

If both conditions are not met the request will be rejected.

Example: myOrder1

cancelOrderId

integer · int64

Example: 1

newClientOrderId

string

Used to identify the new order.

Example: myOrder2

strategyId

integer · int64

Example: 1

strategyType

integer

The value cannot be less than 1000000.

Example: 1

stopPrice

number · float

Example: 1

trailingDelta

integer · int64

See Trailing Stop order FAQ

Example: 1

icebergQty

number · float

Example: 1

newOrderRespType

string · enum

Allowed values:
ACK, RESULT, FULL
MARKET and LIMIT orders types default to FULL; all other orders default to ACK

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. The possible supported values are: STP Modes.

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

cancelRestrictions

string · enum

Supported values:
ONLY_NEW - Cancel will succeed if the order status is NEW.
ONLY_PARTIALLY_FILLED - Cancel will succeed if order status is PARTIALLY_FILLED.

Enum values:

ONLY_NEW

ONLY_PARTIALLY_FILLED

Example: ONLY_NEW

orderRateLimitExceededMode

string · enum

Supported values:
DO_NOTHING (default)- will only attempt to cancel the order if account has not exceeded the unfilled order rate limit
CANCEL_ONLY - will always cancel the order

Enum values:

DO_NOTHING

CANCEL_ONLY

Example: DO_NOTHING

pegPriceType

string · enum

PRIMARY_PEG or MARKET_PEG
See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pegOffsetValue

integer

Price level to peg the price to (max: 100)
See Pegged Orders

Example: 1

pegOffsetType

string · enum

Only PRICE_LEVEL is supported
See Pegged Orders.

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

recvWindow

number · float · max: 60000

Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Data Source: Matching Engine

Similar to POST /api/v3/order, additional mandatory parameters are determined by type. Response format varies depending on whether the processing of the message succeeded, partially succeeded, or failed.

Request			Response
`cancelReplaceMode`	`orderRateLimitExceededMode`	Unfilled Order Count	`cancelResult`	`newOrderResult`	`status`
`STOP_ON_FAILURE`	`DO_NOTHING`	Within Limits	✅ `SUCCESS`	✅ `SUCCESS`	`200`
			❌ `FAILURE`	➖ `NOT_ATTEMPTED`	`400`
			✅ `SUCCESS`	❌ `FAILURE`	`409`
		Exceeds Limits	✅ `SUCCESS`	✅ `SUCCESS`	N/A
			❌ `FAILURE`	➖ `NOT_ATTEMPTED`	N/A
			✅ `SUCCESS`	❌ `FAILURE`	N/A
	`CANCEL_ONLY`	Within Limits	✅ `SUCCESS`	✅ `SUCCESS`	`200`
			❌ `FAILURE`	➖ `NOT_ATTEMPTED`	`400`
			✅ `SUCCESS`	❌ `FAILURE`	`409`
		Exceeds Limits	❌ `FAILURE`	➖ `NOT_ATTEMPTED`	`429`
		Exceeds Limits	✅ `SUCCESS`	❌ `FAILURE`	`429`
`ALLOW_FAILURE`	`DO_NOTHING`	Within Limits	✅ `SUCCESS`	✅ `SUCCESS`	`200`
			❌ `FAILURE`	❌ `FAILURE`	`400`
			❌ `FAILURE`	✅ `SUCCESS`	`409`
			✅ `SUCCESS`	❌ `FAILURE`	`409`
		Exceeds Limits	✅ `SUCCESS`	✅ `SUCCESS`	N/A
			❌ `FAILURE`	❌ `FAILURE`	N/A
			❌ `FAILURE`	✅ `SUCCESS`	N/A
			✅ `SUCCESS`	❌ `FAILURE`	N/A
	`CANCEL_ONLY`	Within Limits	✅ `SUCCESS`	✅ `SUCCESS`	`200`
			❌ `FAILURE`	❌ `FAILURE`	`400`
			❌ `FAILURE`	✅ `SUCCESS`	`409`
			✅ `SUCCESS`	❌ `FAILURE`	`409`
		Exceeds Limits	✅ `SUCCESS`	✅ `SUCCESS`	`N/A`
			❌ `FAILURE`	❌ `FAILURE`	`400`
			❌ `FAILURE`	✅ `SUCCESS`	N/A
			✅ `SUCCESS`	❌ `FAILURE`	`409`

Notes:

The performance for canceling an order (single cancel or as part of a cancel-replace) is always better when only orderId is sent. Sending origClientOrderId or both orderId + origClientOrderId will be slower.

Cancel an Existing Order and Send a New Order › Responses

200

Both cancel and new order succeed

cancelResult

string

Example: SUCCESS

newOrderResult

string

Example: SUCCESS

object

POST/api/v3/order/cancelReplace

curl --request POST \
  --url https://api.binance.com/api/v3/order/cancelReplace \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data side=BUY \
  --data type=MARKET \
  --data cancelReplaceMode=STOP_ON_FAILURE \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "side": "BUY",
  "type": "MARKET",
  "cancelReplaceMode": "STOP_ON_FAILURE",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "cancelResult": "SUCCESS",
  "newOrderResult": "SUCCESS",
  "cancelResponse": {
    "symbol": "BTCUSDT",
    "origClientOrderId": "DnLo3vTAQcjha43lAZhZ0y",
    "orderId": 9,
    "orderListId": -1,
    "clientOrderId": "osxN3JXAtJvKvCqGeMWMVR",
    "transactTime": 1684804350068,
    "price": "0.01000000",
    "origQty": "0.000100",
    "executedQty": "0.00000000",
    "origQuoteOrderQty": "0.000000",
    "cummulativeQuoteQty": "0.00000000",
    "status": "CANCELED",
    "timeInForce": "GTC",
    "type": "LIMIT",
    "side": "SELL",
    "selfTradePreventionMode": "NONE",
    "icebergQty": "0.00000000",
    "preventedMatchId": 0,
    "preventedQuantity": "1.200000",
    "stopPrice": "0.00000000",
    "strategyId": 1,
    "strategyType": 1000000,
    "trailingDelta": 10,
    "trailingTime": -1,
    "usedSor": true,
    "workingFloor": "SOR",
    "pegPriceType": "PRIMARY_PEG",
    "pegOffsetType": "PRICE_LEVEL",
    "pegOffsetValue": 5,
    "peggedPrice": "87523.83710000",
    "expiryReason": "INSUFFICIENT_LIQUIDITY"
  },
  "newOrderResponse": {
    "symbol": "BTCUSDT",
    "orderId": 10,
    "orderListId": -1,
    "clientOrderId": "wOceeeOzNORyLiQfw7jd8S",
    "transactTime": 1652928801803,
    "price": "0.02000000",
    "origQty": "0.040000",
    "executedQty": "0.00000000",
    "origQuoteOrderQty": "0.000000",
    "cummulativeQuoteQty": "0.00000000",
    "status": "NEW",
    "timeInForce": "GTC",
    "type": "LIMIT",
    "side": "BUY",
    "workingTime": 1669277163808,
    "fills": [
      {
        "price": "4000.00000000",
        "qty": "1.00000000",
        "commission": "4.00000000",
        "commissionAsset": "USDT",
        "tradeId": 12345
      }
    ],
    "selfTradePreventionMode": "NONE",
    "icebergQty": "0.00000000",
    "preventedMatchId": 0,
    "preventedQuantity": "1.200000",
    "stopPrice": "0.00000000",
    "strategyId": 1,
    "strategyType": 1000000,
    "trailingDelta": 10,
    "trailingTime": -1,
    "usedSor": true,
    "workingFloor": "SOR",
    "pegPriceType": "PRIMARY_PEG",
    "pegOffsetType": "PRICE_LEVEL",
    "pegOffsetValue": 5,
    "peggedPrice": "87523.83710000",
    "expiryReason": "INSUFFICIENT_LIQUIDITY"
  }
}

json

application/json

New Order list - OCO

Send in an one-cancels-the-other (OCO) pair, where activation of one order immediately cancels the other.

An OCO has 2 orders called the above order and below order.
One of the orders must be a LIMIT_MAKER/TAKE_PROFIT/TAKE_PROFIT_LIMIT order and the other must be STOP_LOSS or STOP_LOSS_LIMIT order.
Price restrictions
- If the OCO is on the SELL side:
  - LIMIT_MAKER/TAKE_PROFIT_LIMIT price > Last Traded Price > STOP_LOSS/STOP_LOSS_LIMIT stopPrice
  - TAKE_PROFIT stopPrice > Last Traded Price > STOP_LOSS/STOP_LOSS_LIMIT stopPrice
- If the OCO is on the BUY side:
  - LIMIT_MAKER/TAKE_PROFIT_LIMIT price < Last Traded Price < stopPrice
  - TAKE_PROFIT stopPrice < Last Traded Price < STOP_LOSS/STOP_LOSS_LIMIT stopPrice * OCOs add 2 orders to the EXCHANGE_MAX_ORDERS filter and the MAX_NUM_ORDERS filter.
OCOs add 2 orders to the EXCHANGE_MAX_ORDERS filter and the MAX_NUM_ORDERS filter.

POST

/api/v3/orderList/oco

https://api.binance.com

Unfilled Order Count2

New Order list - OCO › 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 list - OCO › 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

New Order list - OCO › 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 list - OCO › Request Body

symbol

string · required

Example: BNBUSDT

side

string · enum · required

Enum values:

BUY

SELL

Example: BUY

quantity

number · float · required

Quantity for both orders of the order list.

Example: 1

aboveType

string · enum · required

Enum values:

STOP_LOSS_LIMIT

STOP_LOSS

LIMIT_MAKER

TAKE_PROFIT

TAKE_PROFIT_LIMIT

Example: STOP_LOSS_LIMIT

belowType

string · enum · required

Supported values: STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT

Enum values:

STOP_LOSS

STOP_LOSS_LIMIT

TAKE_PROFIT

TAKE_PROFIT_LIMIT

Example: STOP_LOSS

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

listClientOrderId

string

Arbitrary unique ID among open order lists. Automatically generated if not sent. A new order list with the same listClientOrderId is accepted only when the previous one is filled or completely expired. listClientOrderId is distinct from the aboveClientOrderId and the belowClientOrderId.

Example: lH1YDkuQKWiXVXHPSKYEIp

aboveClientOrderId

string

Arbitrary unique ID among open orders for the above order. Automatically generated if not sent.

Example: aboveOrder1

aboveIcebergQty

integer · int64

Note that this can only be used if aboveTimeInForce is GTC.

Example: 1

abovePrice

number · float

Can be used if aboveType is STOP_LOSS_LIMIT, LIMIT_MAKER, or TAKE_PROFIT_LIMIT to specify the limit price.

Example: 1

aboveStopPrice

number · float

Can be used if aboveType is STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT. Either aboveStopPrice or aboveTrailingDelta or both, must be specified.

Example: 1

aboveTrailingDelta

integer · int64

See Trailing Stop order FAQ

Example: 1

aboveTimeInForce

string · enum

Required if aboveType is STOP_LOSS_LIMIT or TAKE_PROFIT_LIMIT.

Enum values:

GTC

IOC

FOK

Example: GTC

aboveStrategyId

integer · int64

Arbitrary numeric value identifying the above order within an order strategy.

Example: 1

aboveStrategyType

integer

Arbitrary numeric value identifying the above order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

abovePegPriceType

string · enum

PRIMARY_PEG or MARKET_PEG. See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

abovePegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

abovePegOffsetValue

integer

Example: 1

belowClientOrderId

string

Arbitrary unique ID among open orders for the below order. Automatically generated if not sent.

Example: belowOrder1

belowIcebergQty

integer · int64

Note that this can only be used if belowTimeInForce is GTC.

Example: 1

belowPrice

number · float

Can be used if belowType is STOP_LOSS_LIMIT, LIMIT_MAKER, or TAKE_PROFIT_LIMIT to specify the limit price.

Example: 1

belowStopPrice

number · float

Can be used if belowType is STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT. Either belowStopPrice or belowTrailingDelta or both, must be specified.

Example: 1

belowTrailingDelta

integer · int64

See Trailing Stop order FAQ

Example: 1

belowTimeInForce

string · enum

Required if belowType is STOP_LOSS_LIMIT or TAKE_PROFIT_LIMIT.

Enum values:

GTC

IOC

FOK

Example: GTC

belowStrategyId

integer · int64

Arbitrary numeric value identifying the below order within an order strategy.

Example: 1

belowStrategyType

integer

Arbitrary numeric value identifying the below order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

belowPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

belowPegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

belowPegOffsetValue

integer

Example: 1

newOrderRespType

string · enum

Select response format: ACK, RESULT, FULL.

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. Supported values: STP Modes

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

recvWindow

number · float

The value cannot be greater than 60000. Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

New Order list - OCO › Responses

200

New Order list - OCO

orderListId

integer · int64

Example: 1

contingencyType

string

Example: OCO

listStatusType

string

Example: EXEC_STARTED

listOrderStatus

string

Example: EXECUTING

listClientOrderId

string

Example: lH1YDkuQKWiXVXHPSKYEIp

transactionTime

integer · int64

Example: 1710485608839

symbol

string

Example: LTCBTC

object[]

POST/api/v3/orderList/oco

curl --request POST \
  --url https://api.binance.com/api/v3/orderList/oco \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data side=BUY \
  --data quantity=1 \
  --data aboveType=STOP_LOSS_LIMIT \
  --data belowType=STOP_LOSS \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "side": "BUY",
  "quantity": 1,
  "aboveType": "STOP_LOSS_LIMIT",
  "belowType": "STOP_LOSS",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "orderListId": 1,
  "contingencyType": "OCO",
  "listStatusType": "EXEC_STARTED",
  "listOrderStatus": "EXECUTING",
  "listClientOrderId": "lH1YDkuQKWiXVXHPSKYEIp",
  "transactionTime": 1710485608839,
  "symbol": "LTCBTC",
  "orders": [
    {
      "symbol": "LTCBTC",
      "orderId": 10,
      "clientOrderId": "44nZvqpemY7sVYgPYbvPih"
    }
  ],
  "orderReports": [
    {
      "symbol": "LTCBTC",
      "orderId": 10,
      "orderListId": 1,
      "clientOrderId": "44nZvqpemY7sVYgPYbvPih",
      "transactTime": 1710485608839,
      "price": "1.00000000",
      "origQty": "5.00000000",
      "executedQty": "0.00000000",
      "origQuoteOrderQty": "0.000000",
      "cummulativeQuoteQty": "0.00000000",
      "status": "NEW",
      "timeInForce": "GTC",
      "type": "STOP_LOSS_LIMIT",
      "side": "SELL",
      "workingTime": -1,
      "selfTradePreventionMode": "NONE",
      "stopPrice": "1.00000000",
      "icebergQty": "1.00000000"
    }
  ]
}

json

application/json

New Order List - OPO

Place an OPO.

OPOs add 2 orders to the EXCHANGE_MAX_NUM_ORDERS`` filter and MAX_NUM_ORDERS`` filter.

POST

/api/v3/orderList/opo

https://api.binance.com

Unfilled Order Count2

New Order List - OPO › 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 List - OPO › 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

New Order List - OPO › 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 List - OPO › Request Body

symbol

string · required

Example: BNBUSDT

workingType

string · enum · required

Supported values: LIMIT, LIMIT_MAKER

Enum values:

LIMIT

LIMIT_MAKER

Example: LIMIT

workingSide

string · enum · required

Supported values: Order Side

Enum values:

BUY

SELL

Example: BUY

workingPrice

number · float · required

Price for the working order.

Example: 1

workingQuantity

number · float · required

Sets the quantity for the working order.

Example: 1

pendingType

string · enum · required

Supported values: Order Types. Note that MARKET orders using quoteOrderQty are not supported.

Enum values:

LIMIT

MARKET

STOP_LOSS

STOP_LOSS_LIMIT

TAKE_PROFIT

TAKE_PROFIT_LIMIT

LIMIT_MAKER

Example: LIMIT

pendingSide

string · enum · required

Supported values: Order 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

listClientOrderId

string

Example: H94qCqO27P74OEiO4X8HOG

newOrderRespType

string · enum

Format of the JSON response. Supported values: Order Response Type

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. Supported values: STP Modes

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

workingClientOrderId

string

Arbitrary unique ID among open orders for the working order. Automatically generated if not sent.

Example: workingOrder1

workingIcebergQty

number · float

This can only be used if workingTimeInForce is GTC, or if workingType is LIMIT_MAKER.

Example: 1

workingTimeInForce

string · enum

Supported values: Time In Force

Enum values:

GTC

IOC

FOK

Example: GTC

workingStrategyId

integer · int64

Arbitrary numeric value identifying the working order within an order strategy.

Example: 1

workingStrategyType

integer

Arbitrary numeric value identifying the working order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

workingPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

workingPegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

workingPegOffsetValue

integer

Example: 1

pendingClientOrderId

string

Arbitrary unique ID among open orders for the pending order. Automatically generated if not sent.

Example: pendingOrder1

pendingPrice

number · float

Price for the pending order.

Example: 1

pendingStopPrice

number · float

Stop price for the pending order.

Example: 1

pendingTrailingDelta

number · float

Trailing delta for the pending order.

Example: 1

pendingIcebergQty

number · float

This can only be used if pendingTimeInForce is GTC or if pendingType is LIMIT_MAKER.

Example: 1

pendingTimeInForce

string · enum

Supported values: Time In Force

Enum values:

GTC

IOC

FOK

Example: GTC

pendingStrategyId

integer · int64

Arbitrary numeric value identifying the pending order within an order strategy.

Example: 1

pendingStrategyType

integer

Arbitrary numeric value identifying the pending order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

pendingPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pendingPegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

pendingPegOffsetValue

integer

Example: 1

recvWindow

number · float · max: 60000

Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

New Order List - OPO › Responses

200

New Order List - OPO

orderListId

integer · int64

Example: 0

contingencyType

string

Example: OTO

listStatusType

string

Example: EXEC_STARTED

listOrderStatus

string

Example: EXECUTING

listClientOrderId

string

Example: H94qCqO27P74OEiO4X8HOG

transactionTime

integer · int64

Example: 1762998011671

symbol

string

Example: BTCUSDT

object[]

POST/api/v3/orderList/opo

curl --request POST \
  --url https://api.binance.com/api/v3/orderList/opo \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data workingType=LIMIT \
  --data workingSide=BUY \
  --data workingPrice=1 \
  --data workingQuantity=1 \
  --data pendingType=LIMIT \
  --data pendingSide=BUY \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "workingType": "LIMIT",
  "workingSide": "BUY",
  "workingPrice": 1,
  "workingQuantity": 1,
  "pendingType": "LIMIT",
  "pendingSide": "BUY",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "orderListId": 0,
  "contingencyType": "OTO",
  "listStatusType": "EXEC_STARTED",
  "listOrderStatus": "EXECUTING",
  "listClientOrderId": "H94qCqO27P74OEiO4X8HOG",
  "transactionTime": 1762998011671,
  "symbol": "BTCUSDT",
  "orders": [
    {
      "symbol": "BTCUSDT",
      "orderId": 2,
      "clientOrderId": "JX6xfdjo0wysiGumfHNmPu"
    }
  ],
  "orderReports": [
    {
      "symbol": "BTCUSDT",
      "orderId": 2,
      "orderListId": 0,
      "clientOrderId": "JX6xfdjo0wysiGumfHNmPu",
      "transactTime": 1762998011671,
      "price": "102264.00000000",
      "executedQty": "0.00000000",
      "origQuoteOrderQty": "0.00000000",
      "cummulativeQuoteQty": "0.00000000",
      "status": "NEW",
      "timeInForce": "GTC",
      "type": "LIMIT",
      "side": "BUY",
      "workingTime": 1762998011671,
      "selfTradePreventionMode": "NONE",
      "origQty": "0.00060000",
      "icebergQty": "0.00000000",
      "preventedMatchId": 0,
      "preventedQuantity": "1.200000",
      "stopPrice": "0.00000000",
      "strategyId": 1,
      "strategyType": 1000000,
      "trailingDelta": 10,
      "trailingTime": -1,
      "usedSor": true,
      "workingFloor": "SOR",
      "pegPriceType": "PRIMARY_PEG",
      "pegOffsetType": "PRICE_LEVEL",
      "pegOffsetValue": 5,
      "peggedPrice": "87523.83710000",
      "expiryReason": "INSUFFICIENT_LIQUIDITY"
    }
  ]
}

json

application/json

New Order List - OPOCO

Place an OPOCO.

POST

/api/v3/orderList/opoco

https://api.binance.com

Unfilled Order Count3

New Order List - OPOCO › 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 List - OPOCO › 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

New Order List - OPOCO › 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 List - OPOCO › Request Body

symbol

string · required

Example: BNBUSDT

workingType

string · enum · required

Enum values:

LIMIT

LIMIT_MAKER

Example: LIMIT

workingSide

string · enum · required

Supported values: Order Side

Enum values:

BUY

SELL

Example: BUY

workingPrice

number · float · required

Price for the working order.

Example: 1

workingQuantity

number · float · required

Sets the quantity for the working order.

Example: 1

pendingSide

string · enum · required

Supported values: Order Side

Enum values:

BUY

SELL

Example: BUY

pendingAboveType

string · enum · required

Supported values: STOP_LOSS_LIMIT, STOP_LOSS, LIMIT_MAKER, TAKE_PROFIT, TAKE_PROFIT_LIMIT

Enum values:

STOP_LOSS_LIMIT

STOP_LOSS

LIMIT_MAKER

TAKE_PROFIT

TAKE_PROFIT_LIMIT

Example: STOP_LOSS_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

listClientOrderId

string

Example: bcedxMpQG6nFrZUPQyshoL

newOrderRespType

string · enum

Format of the JSON response. Supported values: Order Response Type

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. Supported values: STP Modes

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

workingClientOrderId

string

Arbitrary unique ID among open orders for the working order. Automatically generated if not sent.

Example: workingOrder1

workingIcebergQty

number · float

This can only be used if workingTimeInForce is GTC, or if workingType is LIMIT_MAKER.

Example: 1

workingTimeInForce

string · enum

Supported values: Time In Force

Enum values:

GTC

IOC

FOK

Example: GTC

workingStrategyId

integer · int64

Arbitrary numeric value identifying the working order within an order strategy.

Example: 1

workingStrategyType

integer

Arbitrary numeric value identifying the working order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

workingPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

workingPegOffsetType

string · enum

See Pegged Orders

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

workingPegOffsetValue

integer

Price level for pegging (max: 100). See Pegged Orders

Example: 1

pendingAboveClientOrderId

string

Arbitrary unique ID among open orders for the pending above order. Automatically generated if not sent.

Example: pendingAboveOrder1

pendingAbovePrice

number · float

Can be used if pendingAboveType is STOP_LOSS_LIMIT, LIMIT_MAKER, or TAKE_PROFIT_LIMIT to specify the limit price.

Example: 1

pendingAboveStopPrice

number · float

Can be used if pendingAboveType is STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT.

Example: 1

pendingAboveTrailingDelta

number · float

See Trailing Stop order FAQ

Example: 1

pendingAboveIcebergQty

number · float

This can only be used if pendingAboveTimeInForce is GTC or pendingAboveType is LIMIT_MAKER.

Example: 1

pendingAboveTimeInForce

string · enum

Required if pendingAboveType is STOP_LOSS_LIMIT or TAKE_PROFIT_LIMIT.

Enum values:

GTC

IOC

FOK

Example: GTC

pendingAboveStrategyId

integer · int64

Arbitrary numeric value identifying the pending above order within an order strategy.

Example: 1

pendingAboveStrategyType

integer

Arbitrary numeric value identifying the pending above order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

pendingAbovePegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pendingAbovePegOffsetType

string · enum

See Pegged Orders

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

pendingAbovePegOffsetValue

integer

Price level for pegging (max: 100). See Pegged Orders

Example: 1

pendingBelowType

string · enum

Supported values: STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT

Enum values:

STOP_LOSS

STOP_LOSS_LIMIT

TAKE_PROFIT

TAKE_PROFIT_LIMIT

Example: STOP_LOSS

pendingBelowClientOrderId

string

Arbitrary unique ID among open orders for the pending below order. Automatically generated if not sent.

Example: pendingBelowOrder1

pendingBelowPrice

number · float

Can be used if pendingBelowType is STOP_LOSS_LIMIT or TAKE_PROFIT_LIMIT to specify the limit price.

Example: 1

pendingBelowStopPrice

number · float

Can be used if pendingBelowType is STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT. Either pendingBelowStopPrice or pendingBelowTrailingDelta or both, must be specified.

Example: 1

pendingBelowTrailingDelta

number · float

See Trailing Stop order FAQ

Example: 1

pendingBelowIcebergQty

number · float

This can only be used if pendingBelowTimeInForce is GTC or pendingBelowType is LIMIT_MAKER.

Example: 1

pendingBelowTimeInForce

string · enum

Supported values: Time In Force

Enum values:

GTC

IOC

FOK

Example: GTC

pendingBelowStrategyId

integer · int64

Arbitrary numeric value identifying the pending below order within an order strategy.

Example: 1

pendingBelowStrategyType

integer

Arbitrary numeric value identifying the pending below order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

pendingBelowPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pendingBelowPegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

pendingBelowPegOffsetValue

integer

Example: 1

recvWindow

number · float

The value cannot be greater than 60000. Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

New Order List - OPOCO › Responses

200

New Order List - OPOCO

orderListId

integer · int64

Example: 2

contingencyType

string

Example: OTO

listStatusType

string

Example: EXEC_STARTED

listOrderStatus

string

Example: EXECUTING

listClientOrderId

string

Example: bcedxMpQG6nFrZUPQyshoL

transactionTime

integer · int64

Example: 1763000506354

symbol

string

Example: BTCUSDT

object[]

POST/api/v3/orderList/opoco

curl --request POST \
  --url https://api.binance.com/api/v3/orderList/opoco \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data workingType=LIMIT \
  --data workingSide=BUY \
  --data workingPrice=1 \
  --data workingQuantity=1 \
  --data pendingSide=BUY \
  --data pendingAboveType=STOP_LOSS_LIMIT \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "workingType": "LIMIT",
  "workingSide": "BUY",
  "workingPrice": 1,
  "workingQuantity": 1,
  "pendingSide": "BUY",
  "pendingAboveType": "STOP_LOSS_LIMIT",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "orderListId": 2,
  "contingencyType": "OTO",
  "listStatusType": "EXEC_STARTED",
  "listOrderStatus": "EXECUTING",
  "listClientOrderId": "bcedxMpQG6nFrZUPQyshoL",
  "transactionTime": 1763000506354,
  "symbol": "BTCUSDT",
  "orders": [
    {
      "symbol": "BTCUSDT",
      "orderId": 9,
      "clientOrderId": "OLSBhMWaIlLSzZ9Zm7fnKB"
    }
  ],
  "orderReports": [
    {
      "symbol": "BTCUSDT",
      "orderId": 9,
      "orderListId": 2,
      "clientOrderId": "OLSBhMWaIlLSzZ9Zm7fnKB",
      "transactTime": 1763000506354,
      "price": "102496.00000000",
      "executedQty": "0.00000000",
      "origQuoteOrderQty": "0.00000000",
      "cummulativeQuoteQty": "0.00000000",
      "status": "NEW",
      "timeInForce": "GTC",
      "type": "LIMIT",
      "side": "BUY",
      "workingTime": 1763000506354,
      "selfTradePreventionMode": "NONE",
      "origQty": "0.00170000",
      "icebergQty": "0.00000000",
      "preventedMatchId": 0,
      "preventedQuantity": "1.200000",
      "stopPrice": "0.00000000",
      "strategyId": 1,
      "strategyType": 1000000,
      "trailingDelta": 10,
      "trailingTime": -1,
      "usedSor": true,
      "workingFloor": "SOR",
      "pegPriceType": "PRIMARY_PEG",
      "pegOffsetType": "PRICE_LEVEL",
      "pegOffsetValue": 5,
      "peggedPrice": "87523.83710000",
      "expiryReason": "INSUFFICIENT_LIQUIDITY"
    }
  ]
}

json

application/json

New Order list - OTO

Place an OTO.

An OTO (One-Triggers-the-Other) is an order list comprised of 2 orders.
The first order is called the working order and must be LIMIT or LIMIT_MAKER. Initially, only the working order goes on the order book.
The second order is called the pending order. It can be any order type except for MARKET orders using parameter quoteOrderQty. The pending order is only placed on the order book when the working order gets fully filled.
If either the working order or the pending order is cancelled individually, the other order in the order list will also be canceled or expired.
When the order list is placed, if the working order gets immediately fully filled, the placement response will show the working order as FILLED but the pending order will still appear as PENDING_NEW. You need to query the status of the pending order again to see its updated status.
OTOs add 2 orders to the EXCHANGE_MAX_NUM_ORDERS filter and MAX_NUM_ORDERS filter.

POST

/api/v3/orderList/oto

https://api.binance.com

Unfilled Order Count2

New Order list - OTO › 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 list - OTO › 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

New Order list - OTO › 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 list - OTO › Request Body

symbol

string · required

Example: BNBUSDT

workingType

string · enum · required

Supported values: LIMIT, LIMIT_MAKER

Enum values:

LIMIT

LIMIT_MAKER

Example: LIMIT

workingSide

string · enum · required

Supported values: Order Side

Enum values:

BUY

SELL

Example: BUY

workingPrice

number · float · required

Example: 1

workingQuantity

number · float · required

Sets the quantity for the working order.

Example: 1

pendingType

string · enum · required

Supported values: Order Types. Note that MARKET orders using quoteOrderQty are not supported.

Enum values:

LIMIT

MARKET

STOP_LOSS

STOP_LOSS_LIMIT

TAKE_PROFIT

TAKE_PROFIT_LIMIT

LIMIT_MAKER

Example: LIMIT

pendingSide

string · enum · required

Supported values: Order Side

Enum values:

BUY

SELL

Example: BUY

pendingQuantity

number · float · required

Sets the quantity for the pending order.

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

listClientOrderId

string

Example: yl2ERtcar1o25zcWtqVBTC

newOrderRespType

string · enum

Format of the JSON response. Supported values: Order Response Type

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. Supported values: STP Modes

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

workingClientOrderId

string

Arbitrary unique ID among open orders for the working order. Automatically generated if not sent.

Example: workingOrder1

workingIcebergQty

number · float

This can only be used if workingTimeInForce is GTC, or if workingType is LIMIT_MAKER.

Example: 1

workingTimeInForce

string · enum

Supported values: Time In Force

Enum values:

GTC

IOC

FOK

Example: GTC

workingStrategyId

integer · int64

Arbitrary numeric value identifying the working order within an order strategy.

Example: 1

workingStrategyType

integer

Arbitrary numeric value identifying the working order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

workingPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

workingPegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

workingPegOffsetValue

integer

Example: 1

pendingClientOrderId

string

Arbitrary unique ID among open orders for the pending order. Automatically generated if not sent.

Example: pendingOrder1

pendingPrice

number · float

Example: 1

pendingStopPrice

number · float

Example: 1

pendingTrailingDelta

number · float

Example: 1

pendingIcebergQty

number · float

This can only be used if pendingTimeInForce is GTC or if pendingType is LIMIT_MAKER.

Example: 1

pendingTimeInForce

string · enum

Supported values: Time In Force

Enum values:

GTC

IOC

FOK

Example: GTC

pendingStrategyId

integer · int64

Arbitrary numeric value identifying the pending order within an order strategy.

Example: 1

pendingStrategyType

integer

Arbitrary numeric value identifying the pending order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

pendingPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pendingPegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

pendingPegOffsetValue

integer

Example: 1

recvWindow

number · float

The value cannot be greater than 60000. Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Data Source: Matching Engine

Mandatory parameters based on pendingType or workingType

Depending on the pendingType or workingType, some optional parameters will become mandatory.

Type	Additional mandatory parameters	Additional information
`workingType` = `LIMIT`	`workingTimeInForce`
`pendingType` = `LIMIT`	`pendingPrice`, `pendingTimeInForce`
`pendingType` = `STOP_LOSS` or `TAKE_PROFIT`	`pendingStopPrice` and/or `pendingTrailingDelta`
`pendingType` = `STOP_LOSS_LIMIT` or `TAKE_PROFIT_LIMIT`	`pendingPrice`, `pendingStopPrice` and/or `pendingTrailingDelta`, `pendingTimeInForce`

New Order list - OTO › Responses

200

New Order list - OTO

orderListId

integer · int64

Example: 0

contingencyType

string

Example: OTO

listStatusType

string

Example: EXEC_STARTED

listOrderStatus

string

Example: EXECUTING

listClientOrderId

string

Example: yl2ERtcar1o25zcWtqVBTC

transactionTime

integer · int64

Example: 1712289389158

symbol

string

Example: LTCBTC

object[]

POST/api/v3/orderList/oto

curl --request POST \
  --url https://api.binance.com/api/v3/orderList/oto \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data workingType=LIMIT \
  --data workingSide=BUY \
  --data workingPrice=1 \
  --data workingQuantity=1 \
  --data pendingType=LIMIT \
  --data pendingSide=BUY \
  --data pendingQuantity=1 \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "workingType": "LIMIT",
  "workingSide": "BUY",
  "workingPrice": 1,
  "workingQuantity": 1,
  "pendingType": "LIMIT",
  "pendingSide": "BUY",
  "pendingQuantity": 1,
  "timestamp": 1770736694138
}

json

Example Responses

{
  "orderListId": 0,
  "contingencyType": "OTO",
  "listStatusType": "EXEC_STARTED",
  "listOrderStatus": "EXECUTING",
  "listClientOrderId": "yl2ERtcar1o25zcWtqVBTC",
  "transactionTime": 1712289389158,
  "symbol": "LTCBTC",
  "orders": [
    {
      "symbol": "LTCBTC",
      "orderId": 4,
      "clientOrderId": "Bq17mn9fP6vyCn75Jw1xya"
    }
  ],
  "orderReports": [
    {
      "symbol": "LTCBTC",
      "orderId": 4,
      "orderListId": 0,
      "clientOrderId": "Bq17mn9fP6vyCn75Jw1xya",
      "transactTime": 1712289389158,
      "price": "1.00000000",
      "origQty": "1.00000000",
      "executedQty": "0.00000000",
      "origQuoteOrderQty": "0.000000",
      "cummulativeQuoteQty": "0.00000000",
      "status": "NEW",
      "timeInForce": "GTC",
      "type": "LIMIT",
      "side": "SELL",
      "workingTime": 1712289389158,
      "selfTradePreventionMode": "NONE",
      "icebergQty": "0.00000000",
      "preventedMatchId": 0,
      "preventedQuantity": "1.200000",
      "stopPrice": "0.00000000",
      "strategyId": 1,
      "strategyType": 1000000,
      "trailingDelta": 10,
      "trailingTime": -1,
      "usedSor": true,
      "workingFloor": "SOR",
      "pegPriceType": "PRIMARY_PEG",
      "pegOffsetType": "PRICE_LEVEL",
      "pegOffsetValue": 5,
      "peggedPrice": "87523.83710000",
      "expiryReason": "INSUFFICIENT_LIQUIDITY"
    }
  ]
}

json

application/json

New Order list - OTOCO

Place an OTOCO.

An OTOCO (One-Triggers-One-Cancels-the-Other) is an order list comprised of 3 orders.
The first order is called the working order and must be LIMIT or LIMIT_MAKER. Initially, only the working order goes on the order book.
- The behavior of the working order is the same as the OTO.
OTOCO has 2 pending orders (pending above and pending below), forming an OCO pair. The pending orders are only placed on the order book when the working order gets fully filled.
- The rules of the pending above and pending below follow the same rules as the Order list OCO.
OTOCOs add 3 orders to the EXCHANGE_MAX_NUM_ORDERS filter and MAX_NUM_ORDERS filter.

POST

/api/v3/orderList/otoco

https://api.binance.com

Unfilled Order Count3

New Order list - OTOCO › 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 list - OTOCO › 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

New Order list - OTOCO › 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 list - OTOCO › Request Body

symbol

string · required

Example: BNBUSDT

workingType

string · enum · required

Supported values: LIMIT, LIMIT_MAKER

Enum values:

LIMIT

LIMIT_MAKER

Example: LIMIT

workingSide

string · enum · required

Supported values: Order Side

Enum values:

BUY

SELL

Example: BUY

workingPrice

number · float · required

Example: 1

workingQuantity

number · float · required

Sets the quantity for the working order.

Example: 1

pendingSide

string · enum · required

Supported values: Order Side

Enum values:

BUY

SELL

Example: BUY

pendingQuantity

number · float · required

Sets the quantity for the pending orders.

Example: 1

pendingAboveType

string · enum · required

Supported values: STOP_LOSS_LIMIT, STOP_LOSS, LIMIT_MAKER, TAKE_PROFIT, TAKE_PROFIT_LIMIT

Enum values:

STOP_LOSS_LIMIT

STOP_LOSS

LIMIT_MAKER

TAKE_PROFIT

TAKE_PROFIT_LIMIT

Example: STOP_LOSS_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

listClientOrderId

string

Example: RumwQpBaDctlUu5jyG5rs0

newOrderRespType

string · enum

Format of the JSON response. Supported values: Order Response Type

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. Supported values: STP Modes

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

workingClientOrderId

string

Arbitrary unique ID among open orders for the working order. Automatically generated if not sent.

Example: workingOrder1

workingIcebergQty

number · float

This can only be used if workingTimeInForce is GTC, or if workingType is LIMIT_MAKER.

Example: 1

workingTimeInForce

string · enum

Supported values: Time In Force

Enum values:

GTC

IOC

FOK

Example: GTC

workingStrategyId

integer · int64

Arbitrary numeric value identifying the working order within an order strategy.

Example: 1

workingStrategyType

integer

Arbitrary numeric value identifying the working order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

workingPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

workingPegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

workingPegOffsetValue

integer

Example: 1

pendingAboveClientOrderId

string

Arbitrary unique ID among open orders for the pending above order. Automatically generated if not sent.

Example: pendingAboveOrder1

pendingAbovePrice

number · float

Can be used if pendingAboveType is STOP_LOSS_LIMIT, LIMIT_MAKER, or TAKE_PROFIT_LIMIT to specify the limit price.

Example: 1

pendingAboveStopPrice

number · float

Can be used if pendingAboveType is STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT.

Example: 1

pendingAboveTrailingDelta

number · float

See Trailing Stop order FAQ

Example: 1

pendingAboveIcebergQty

number · float

This can only be used if pendingAboveTimeInForce is GTC or if pendingAboveType is LIMIT_MAKER.

Example: 1

pendingAboveTimeInForce

string · enum

Required if pendingAboveType is STOP_LOSS_LIMIT or TAKE_PROFIT_LIMIT.

Enum values:

GTC

IOC

FOK

Example: GTC

pendingAboveStrategyId

integer · int64

Arbitrary numeric value identifying the pending above order within an order strategy.

Example: 1

pendingAboveStrategyType

integer

Arbitrary numeric value identifying the pending above order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

pendingAbovePegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pendingAbovePegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

pendingAbovePegOffsetValue

integer

Example: 1

pendingBelowType

string · enum

Supported values: STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT

Enum values:

STOP_LOSS

STOP_LOSS_LIMIT

TAKE_PROFIT

TAKE_PROFIT_LIMIT

Example: STOP_LOSS

pendingBelowClientOrderId

string

Arbitrary unique ID among open orders for the pending below order. Automatically generated if not sent.

Example: pendingBelowOrder1

pendingBelowPrice

number · float

Can be used if pendingBelowType is STOP_LOSS_LIMIT or TAKE_PROFIT_LIMIT to specify the limit price.

Example: 1

pendingBelowStopPrice

number · float

Can be used if pendingBelowType is STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, TAKE_PROFIT_LIMIT. Either pendingBelowStopPrice or pendingBelowTrailingDelta or both, must be specified.

Example: 1

pendingBelowTrailingDelta

number · float

See Trailing Stop order FAQ

Example: 1

pendingBelowIcebergQty

number · float

This can only be used if pendingBelowTimeInForce is GTC, or if pendingBelowType is LIMIT_MAKER.

Example: 1

pendingBelowTimeInForce

string · enum

Required if pendingBelowType is STOP_LOSS_LIMIT or TAKE_PROFIT_LIMIT.

Enum values:

GTC

IOC

FOK

Example: GTC

pendingBelowStrategyId

integer · int64

Arbitrary numeric value identifying the pending below order within an order strategy.

Example: 1

pendingBelowStrategyType

integer

Arbitrary numeric value identifying the pending below order strategy. Values smaller than 1000000 are reserved and cannot be used.

Example: 1

pendingBelowPegPriceType

string · enum

See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pendingBelowPegOffsetType

string · enum

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

pendingBelowPegOffsetValue

integer

Example: 1

recvWindow

number · float

The value cannot be greater than 60000. Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Data Source: Matching Engine

Mandatory parameters based on pendingAboveType, pendingBelowType or workingType

Depending on the pendingAboveType/pendingBelowType or workingType, some optional parameters will become mandatory.

Type	Additional mandatory parameters	Additional information
`workingType` = `LIMIT`	`workingTimeInForce`
`pendingAboveType`= `LIMIT_MAKER`	`pendingAbovePrice`
`pendingAboveType` = `STOP_LOSS/TAKE_PROFIT`	`pendingAboveStopPrice` and/or `pendingAboveTrailingDelta`
`pendingAboveType=STOP_LOSS_LIMIT/TAKE_PROFIT_LIMIT`	`pendingAbovePrice`, `pendingAboveStopPrice` and/or `pendingAboveTrailingDelta`, `pendingAboveTimeInForce`
`pendingBelowType`= `LIMIT_MAKER`	`pendingBelowPrice`
`pendingBelowType= STOP_LOSS/TAKE_PROFIT`	`pendingBelowStopPrice` and/or `pendingBelowTrailingDelta`
`pendingBelowType=STOP_LOSS_LIMIT/TAKE_PROFIT_LIMIT`	`pendingBelowPrice`, `pendingBelowStopPrice` and/or `pendingBelowTrailingDelta`, `pendingBelowTimeInForce`

New Order list - OTOCO › Responses

200

New Order list - OTOCO

orderListId

integer · int64

Example: 1

contingencyType

string

Example: OTO

listStatusType

string

Example: EXEC_STARTED

listOrderStatus

string

Example: EXECUTING

listClientOrderId

string

Example: RumwQpBaDctlUu5jyG5rs0

transactionTime

integer · int64

Example: 1712291372842

symbol

string

Example: LTCBTC

object[]

POST/api/v3/orderList/otoco

curl --request POST \
  --url https://api.binance.com/api/v3/orderList/otoco \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data workingType=LIMIT \
  --data workingSide=BUY \
  --data workingPrice=1 \
  --data workingQuantity=1 \
  --data pendingSide=BUY \
  --data pendingQuantity=1 \
  --data pendingAboveType=STOP_LOSS_LIMIT \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "workingType": "LIMIT",
  "workingSide": "BUY",
  "workingPrice": 1,
  "workingQuantity": 1,
  "pendingSide": "BUY",
  "pendingQuantity": 1,
  "pendingAboveType": "STOP_LOSS_LIMIT",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "orderListId": 1,
  "contingencyType": "OTO",
  "listStatusType": "EXEC_STARTED",
  "listOrderStatus": "EXECUTING",
  "listClientOrderId": "RumwQpBaDctlUu5jyG5rs0",
  "transactionTime": 1712291372842,
  "symbol": "LTCBTC",
  "orders": [
    {
      "symbol": "LTCBTC",
      "orderId": 6,
      "clientOrderId": "fM9Y4m23IFJVCQmIrlUmMK"
    }
  ],
  "orderReports": [
    {
      "symbol": "LTCBTC",
      "orderId": 6,
      "orderListId": 1,
      "clientOrderId": "fM9Y4m23IFJVCQmIrlUmMK",
      "transactTime": 1712291372842,
      "price": "1.00000000",
      "origQty": "1.00000000",
      "executedQty": "0.00000000",
      "origQuoteOrderQty": "0.000000",
      "cummulativeQuoteQty": "0.00000000",
      "status": "NEW",
      "timeInForce": "GTC",
      "type": "LIMIT",
      "side": "SELL",
      "workingTime": 1712291372842,
      "selfTradePreventionMode": "NONE",
      "icebergQty": "0.00000000",
      "preventedMatchId": 0,
      "preventedQuantity": "1.200000",
      "stopPrice": "0.00000000",
      "strategyId": 1,
      "strategyType": 1000000,
      "trailingDelta": 10,
      "trailingTime": -1,
      "usedSor": true,
      "workingFloor": "SOR",
      "pegPriceType": "PRIMARY_PEG",
      "pegOffsetType": "PRICE_LEVEL",
      "pegOffsetValue": 5,
      "peggedPrice": "87523.83710000",
      "expiryReason": "INSUFFICIENT_LIQUIDITY"
    }
  ]
}

json

application/json

deprecated

New OCO - Deprecated

Send in a new OCO.

Price Restrictions:
- SELL: Limit Price > Last Price > Stop Price
- BUY: Limit Price < Last Price < Stop Price
Quantity Restrictions:
- Both legs must have the same quantity.
- ICEBERG quantities however do not have to be the same
OCO adds 2 orders to the EXCHANGE_MAX_ORDERS filter and the MAX_NUM_ORDERS filter.

POST

/api/v3/order/oco

https://api.binance.com

Unfilled Order Count2

New OCO - Deprecated › 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 OCO - Deprecated › 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

New OCO - Deprecated › 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 OCO - Deprecated › Request Body

symbol

string · required

Example: BNBUSDT

side

string · enum · required

Enum values:

BUY

SELL

Example: BUY

quantity

number · float · required

Example: 1

price

number · float · required

Example: 1

stopPrice

number · float · required

Example: 1

timestamp

integer · int64 · required

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

Example: 1770736694138

listClientOrderId

string

A unique Id for the entire orderList

Example: JYVpp3F0f5CAG15DhtrqLp

limitClientOrderId

string

A unique Id for the limit order

Example: limitOrder1

limitStrategyId

integer · int64

Example: 1

limitStrategyType

integer

The value cannot be less than 1000000.

Example: 1

limitIcebergQty

number · float

Used to make the LIMIT_MAKER leg an iceberg order.

Example: 1

trailingDelta

integer · int64

Example: 1

stopClientOrderId

string

A unique Id for the stop loss/stop loss limit leg

Example: stopOrder1

stopStrategyId

integer · int64

Example: 1

stopStrategyType

integer

The value cannot be less than 1000000.

Example: 1

stopLimitPrice

number · float

If provided, stopLimitTimeInForce is required.

Example: 1

stopIcebergQty

number · float

Used with STOP_LOSS_LIMIT leg to make an iceberg order.

Example: 1

stopLimitTimeInForce

string · enum

Valid values are GTC/FOK/IOC

Enum values:

GTC

IOC

FOK

Example: GTC

newOrderRespType

string · enum

Format of the JSON response. Supported values: Order Response Type

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed values are dependent on what is configured on the symbol. Supported values: STP Modes

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

recvWindow

number · float

The value cannot be greater than 60000.
Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

New OCO - Deprecated › Responses

200

New OCO - Deprecated

orderListId

integer · int64

Example: 0

contingencyType

string

Example: OCO

listStatusType

string

Example: EXEC_STARTED

listOrderStatus

string

Example: EXECUTING

listClientOrderId

string

Example: JYVpp3F0f5CAG15DhtrqLp

transactionTime

integer · int64

Example: 1563417480525

symbol

string

Example: LTCBTC

object[]

POST/api/v3/order/oco

curl --request POST \
  --url https://api.binance.com/api/v3/order/oco \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data side=BUY \
  --data quantity=1 \
  --data price=1 \
  --data stopPrice=1 \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "side": "BUY",
  "quantity": 1,
  "price": 1,
  "stopPrice": 1,
  "timestamp": 1770736694138
}

json

Example Responses

{
  "orderListId": 0,
  "contingencyType": "OCO",
  "listStatusType": "EXEC_STARTED",
  "listOrderStatus": "EXECUTING",
  "listClientOrderId": "JYVpp3F0f5CAG15DhtrqLp",
  "transactionTime": 1563417480525,
  "symbol": "LTCBTC",
  "orders": [
    {
      "symbol": "LTCBTC",
      "orderId": 2,
      "clientOrderId": "Kk7sqHb9J6mJWTMDVW7Vos"
    }
  ],
  "orderReports": [
    {
      "symbol": "LTCBTC",
      "orderId": 2,
      "orderListId": 0,
      "clientOrderId": "Kk7sqHb9J6mJWTMDVW7Vos",
      "transactTime": 1563417480525,
      "price": "0.000000",
      "origQty": "0.624363",
      "executedQty": "0.000000",
      "origQuoteOrderQty": "0.000000",
      "cummulativeQuoteQty": "0.000000",
      "status": "NEW",
      "timeInForce": "GTC",
      "type": "STOP_LOSS",
      "side": "BUY",
      "workingTime": -1,
      "selfTradePreventionMode": "NONE",
      "stopPrice": "0.960664"
    }
  ]
}

json

application/json

Test new order

Test new order creation and signature/recvWindow long.

Creates and validates a new order but does not send it into the matching engine.

POST

/api/v3/order/test

https://api.binance.com

Test new order › 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

Test new order › 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

Condition	Weight
Without `computeCommissionRates`	1
With `computeCommissionRates`	20

Test new order › 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

Test new order › Request Body

symbol

string · required

Example: BNBUSDT

side

string · enum · required

Please see Enums for supported values.

Enum values:

BUY

SELL

Example: BUY

type

string · enum · required

Please see Enums for supported values.

Enum values:

MARKET

LIMIT

STOP_LOSS

STOP_LOSS_LIMIT

TAKE_PROFIT

TAKE_PROFIT_LIMIT

LIMIT_MAKER

Example: MARKET

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

computeCommissionRates

boolean

Default: false
See Commissions FAQ to learn more.

Example: false

timeInForce

string · enum

Please see Enums for supported values.

Enum values:

GTC

IOC

FOK

Example: GTC

quantity

number · float

Example: 1

quoteOrderQty

number · float

Example: 1

price

number · float

Example: 400

newClientOrderId

string

A unique id among open orders. Automatically generated if not sent. Orders with the same newClientOrderID can be accepted only when the previous one is filled, otherwise the order will be rejected.

Example: myOrder1

strategyId

integer · int64

Example: 1

strategyType

integer

The value cannot be less than 1000000.

Example: 1

stopPrice

number · float

Used with STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT, and TAKE_PROFIT_LIMIT orders.

Example: 1

trailingDelta

integer · int64

See Trailing Stop order FAQ

Example: 1

icebergQty

number · float

Used with LIMIT, STOP_LOSS_LIMIT, and TAKE_PROFIT_LIMIT to create an iceberg order.

Example: 1

newOrderRespType

string · enum

Set the response JSON. ACK, RESULT, or FULL; MARKET and LIMIT order types default to FULL, all other orders default to ACK.

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. Supported values: STP Modes

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

pegPriceType

string · enum

PRIMARY_PEG or MARKET_PEG. See Pegged Orders

Enum values:

PRIMARY_PEG

MARKET_PEG

Example: PRIMARY_PEG

pegOffsetValue

integer

Price level for pegging (max: 100). See Pegged Orders

Example: 1

pegOffsetType

string · enum

Only PRICE_LEVEL is supported. See Pegged Orders

Enum values:

PRICE_LEVEL

Example: PRICE_LEVEL

recvWindow

number · float

The value cannot be greater than 60000. Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Test new order › Responses

200

Test new order

object

Standard commission rates on trades from the order.

object

Special commission rates on trades from the order.

object

Tax commission rates for trades from the order.

object

Discount on standard commissions when paying in BNB.

POST/api/v3/order/test

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

Example Request Body

{
  "symbol": "BNBUSDT",
  "side": "BUY",
  "type": "MARKET",
  "timestamp": 1770736694138
}

json

Example Responses

{
  "standardCommissionForOrder": {
    "maker": 0.00000112,
    "taker": 0.00000114
  },
  "specialCommissionForOrder": {
    "maker": 0.05,
    "taker": 0.06
  },
  "taxCommissionForOrder": {
    "maker": 0.00000112,
    "taker": 0.00000114
  },
  "discount": {
    "enabledForAccount": true,
    "enabledForSymbol": true,
    "discountAsset": "BNB",
    "discount": 0.25
  }
}

json

application/json

New order using SOR

Places an order using smart order routing (SOR).

This adds 1 order to the EXCHANGE_MAX_ORDERS filter and the MAX_NUM_ORDERS filter.

Read SOR FAQ to learn more.

POST

/api/v3/sor/order

https://api.binance.com

Unfilled Order Count1

New order using SOR › 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 using SOR › 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

New order using SOR › 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 using SOR › Request Body

symbol

string · required

Example: BNBUSDT

side

string · enum · required

Enum values:

BUY

SELL

Example: BUY

type

string · enum · required

Enum values:

MARKET

LIMIT

Example: MARKET

quantity

number · float · required

Example: 1

timestamp

integer · int64 · required

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

Example: 1770736694138

timeInForce

string · enum

Enum values:

GTC

IOC

FOK

Example: GTC

price

number · float

Example: 400

newClientOrderId

string

A unique id among open orders. Automatically generated if not sent.
Orders with the same newClientOrderID can be accepted only when the previous one is filled, otherwise the order will be rejected.

Example: myOrder1

strategyId

integer · int64

Example: 1

strategyType

integer

The value cannot be less than 1000000.

Example: 1

icebergQty

number · float

Used with LIMIT to create an iceberg order.

Example: 1

newOrderRespType

string · enum

Set the response JSON. ACK, RESULT, or FULL. Default to FULL

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. The possible supported values are: STP Modes.

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

recvWindow

number · float

The value cannot be greater than 60000.
Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

New order using SOR › Responses

200

New order using SOR

symbol

string

Example: BTCUSDT

orderId

integer · int64

Example: 2

orderListId

integer · int64

Example: -1

clientOrderId

string

Example: sBI1KM6nNtOfj5tccZSKly

transactTime

integer · int64

Example: 1689149087774

price

string

Example: 31000.00000000

origQty

string

Example: 0.50000000

executedQty

string

Example: 0.50000000

origQuoteOrderQty

string

Example: 0.000000

cummulativeQuoteQty

string

Example: 14000.00000000

status

string

Example: FILLED

timeInForce

string

Example: GTC

type

string

Example: LIMIT

side

string

Example: BUY

workingTime

integer · int64

Example: 1689149087774

object[]

workingFloor

string

Example: SOR

selfTradePreventionMode

string

Example: NONE

usedSor

boolean

Example: true

POST/api/v3/sor/order

curl --request POST \
  --url https://api.binance.com/api/v3/sor/order \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data side=BUY \
  --data type=MARKET \
  --data quantity=1 \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "side": "BUY",
  "type": "MARKET",
  "quantity": 1,
  "timestamp": 1770736694138
}

json

Example Responses

{
  "symbol": "BTCUSDT",
  "orderId": 2,
  "orderListId": -1,
  "clientOrderId": "sBI1KM6nNtOfj5tccZSKly",
  "transactTime": 1689149087774,
  "price": "31000.00000000",
  "origQty": "0.50000000",
  "executedQty": "0.50000000",
  "origQuoteOrderQty": "0.000000",
  "cummulativeQuoteQty": "14000.00000000",
  "status": "FILLED",
  "timeInForce": "GTC",
  "type": "LIMIT",
  "side": "BUY",
  "workingTime": 1689149087774,
  "fills": [
    {
      "matchType": "ONE_PARTY_TRADE_REPORT",
      "price": "28000.00000000",
      "qty": "0.50000000",
      "commission": "0.00000000",
      "commissionAsset": "BTC",
      "tradeId": -1,
      "allocId": 0
    }
  ],
  "workingFloor": "SOR",
  "selfTradePreventionMode": "NONE",
  "usedSor": true
}

json

application/json

Test new order using SOR

Test new order creation and signature/recvWindow using smart order routing (SOR). Creates and validates a new order but does not send it into the matching engine.

POST

/api/v3/sor/order/test

https://api.binance.com

Test new order using SOR › 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

Test new order using SOR › 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

Condition	Weight
Without `computeCommissionRates`	1
With `computeCommissionRates`	20

Test new order using SOR › 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

Test new order using SOR › Request Body

symbol

string · required

Example: BNBUSDT

side

string · enum · required

Please see Enums for supported values.

Enum values:

BUY

SELL

Example: BUY

type

string · enum · required

Please see Enums for supported values.

Enum values:

MARKET

LIMIT

Example: MARKET

quantity

number · float · required

Example: 1

timestamp

integer · int64 · required

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

Example: 1770736694138

computeCommissionRates

boolean

Example: false

Default: false

timeInForce

string · enum

Please see Enums for supported values.

Enum values:

GTC

IOC

FOK

Example: GTC

price

number · float

Example: 400

newClientOrderId

string

A unique id among open orders. Automatically generated if not sent. Orders with the same newClientOrderID can be accepted only when the previous one is filled, otherwise the order will be rejected.

Example: myOrder1

strategyId

integer · int64

Example: 1

strategyType

integer

The value cannot be less than 1000000.

Example: 1

icebergQty

number · float

Used with LIMIT to create an iceberg order.

Example: 1

newOrderRespType

string · enum

Set the response JSON. ACK, RESULT, or FULL. Default to FULL.

Enum values:

ACK

RESULT

FULL

Example: ACK

selfTradePreventionMode

string · enum

The allowed enums is dependent on what is configured on the symbol. Supported values: STP Modes

Enum values:

NONE

EXPIRE_TAKER

EXPIRE_MAKER

EXPIRE_BOTH

DECREMENT

TRANSFER

Example: NONE

recvWindow

number · float

The value cannot be greater than 60000. Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified.

Example: 5000

Test new order using SOR › Responses

200

Test new order using SOR

object

Standard commission rates on trades from the order.

object

Tax commission rates for trades from the order.

object

Discount on standard commissions when paying in BNB.

POST/api/v3/sor/order/test

curl --request POST \
  --url https://api.binance.com/api/v3/sor/order/test \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'X-MBX-APIKEY: <string>' \
  --data symbol=BNBUSDT \
  --data side=BUY \
  --data type=MARKET \
  --data quantity=1 \
  --data timestamp=1770736694138

Example Request Body

{
  "symbol": "BNBUSDT",
  "side": "BUY",
  "type": "MARKET",
  "quantity": 1,
  "timestamp": 1770736694138
}

json

Example Responses

{
  "standardCommissionForOrder": {
    "maker": 0.00000112,
    "taker": 0.00000114
  },
  "taxCommissionForOrder": {
    "maker": 0.00000112,
    "taker": 0.00000114
  },
  "discount": {
    "enabledForAccount": true,
    "enabledForSymbol": true,
    "discountAsset": "BNB",
    "discount": 0.25
  }
}

json

application/json