BUbullish
orders

Cancel Order Commands

Submits a command to the trading engine. A successful response indicates that the command entry was acknowledged but does not indicate that the command was executed. This endpoint uses the signing format which does not require strict field ordering and addition of null fields in the request body. Quantities and prices does not require strict precision. E.g. for asset precision of 4 - 100, 100.0, 100.00, 100.000 and 100.0000 are all accepted.

Command schemas and examples are provided below. Supported commands:

  • V3CancelOrder
  • V1CancelAllOrders
  • V1CancelAllOrdersByMarket
  • V1DelayedCancelAllOrders
  • V1UnsetDelayedCancelAllOrders

Requires

  • bearer token in authorization header

Ratelimited: True. Higher tiers of rate limits available by providing the BX-RATELIMIT-TOKEN request header.

post/v2/command#cancellations

Request

Headers

BX-SIGNATUREstring required

signature obtained using the signing format

BX-TIMESTAMPstring required

timestamp is the number of milliseconds since EPOCH

BX-NONCEstring required

nonce is a client side incremented unsigned 64 bit integer

BX-NONCE-WINDOW-ENABLED'false' | 'true'

string representation of a boolean value, enables out-of-order order requests to be processed

Request body

OR
OR
OR
OR

Example request

{
  "commandType": "V3CancelOrder",
  "orderId": "297735387747975680",
  "symbol": "BTCUSDC",
  "tradingAccountId": "111000000000001"
}

Response

Status OK. This means a command was successfully acknowledged.

OR
OR
OR
OR

Example response

{
  "commandType": "V3CancelOrder",
  "message": "Command acknowledged - CancelOrder",
  "requestId": "633910976353665024",
  "orderId": "633910775316480001"
}

Changes

No recorded changes to this operation across all 1 revision of this API.