Order Updates (Private)
Automatically subscribed after successful authentication, pushes user futures order status changes.
- Channel:
order - Push Frequency: Real-time, unthrottled
- Access: Private (
authrequired)
Authentication
Use the standard HmacSHA256 WebSocket login request described in Common Module · WebSocket Interface.
After successful authentication,
order,balance, andpositionare subscribed automatically.
Push Example
{
"ch": "order",
"d": {
"e": "order",
"i": "1234567890",
"c": "",
"s": "BTC_USDT",
"S": 1,
"T": 1,
"p": "49000",
"q": "0.1",
"Q": "",
"z": "0.1",
"Z": "4900",
"o": 2,
"f": "4.9",
"F": "USDT",
"C": 1768205315166,
"u": 1768205315166
}
}
Push Fields
| Field | Type | Description |
|---|---|---|
e | string | Event type, fixed as "order" |
i | string | Order ID |
c | string | Client order ID (optional) |
s | string | Trading pair |
S | number | Side: 1=buy, 2=sell |
T | number | Type: 1=limit, 2=market buy, 3=market sell |
p | string | Order price |
q | string | Order quantity |
Q | string | Order amount (used for market buy) |
z | string | Filled quantity |
Z | string | Filled amount |
o | number | Status: 1=new, 2=partially filled, 3=filled, 4=canceled |
f | string | Accumulated fee |
F | string | Fee asset |
C | number | Creation time (milliseconds) |
u | number | Update time (milliseconds) |