Order Cancelled (452)
Sent when one of your orders is cancelled. Requires an authenticated connection; there is no subscription for it.
The REST response is the authoritative confirmation of your request. WebSocket events confirm the same change shortly afterwards; do not wait for them before considering an order placed or cancelled.
[452, {
"type": 452, "id": 123456789, "userId": 12345,
"pairId": 19, "symbol": "BTCUSDT",
"method": 0, "orderType": 0,
"price": "85400", "amount": "0.1",
"numLeft": "0.1", "denomLeft": "8540",
"newOrderClientId": "my-client-id"
}]
| Field | Description |
|---|---|
id | Order id. |
userId | Your user id. |
pairId | Pair id. |
symbol | Pair symbol. |
method | 0 limit, 1 market, 2 stopLimit, 3 stopMarket. |
orderType | 0 buy, 1 sell. |
price | Order price. |
amount | Order amount, in the numerator (base) asset. |
numLeft | Unfilled amount still on the order. |
denomLeft | Order total in the denominator (quote) asset. |
newOrderClientId | Your client id, when one was supplied. |
Despite the symmetry of their names, numLeft and denomLeft are not the same kind of value:
numLeft is what remains unfilled, while denomLeft is the order's total quote value - not a
remainder. Do not compute a fill ratio from the two.
Unlike the market-data channels, these values are plain decimal strings with no fixed number of decimals - do not assume a fixed scale when parsing.
An order cancelled through Cancel Orders produces a 452.
That push is the confirmation that the cancellation was applied - you do not need to poll for it,
though polling remains a safe fallback if your connection dropped.
Order Inserted carries an identical payload
under type 451.
Numbers in private messages can carry trailing zeros (for example 156.6400000000000000). Always parse them as decimals.