user.order
CHANNELOrder updates for the user. Subscribe with channel ["user.order"]. Initial response with same id contains current open orders; subsequent messages (id -1) are live updates.wss://stream.crypto.com/fcm/v1/user
user.orderPrivate
Request
Body
required
Request id
Possible values: [subscribe]
params objectrequired
e.g. ["user.order"]
Current timestamp in milliseconds
Schema
- Array [
- ➖ LIMIT, MARKET
- ➖ STOP, STOP_LIMIT: Trigger orders
- ]
result object
data object[]
Account ID.
Order ID.
Client Order ID.
Possible values: [LIMIT, MARKET, STOP, STOP_LIMIT]
Order type:
Possible values: [IMMEDIATE_OR_CANCEL]
Time in force. Only IMMEDIATE_OR_CANCEL (IOC) is accepted for Combo orders.
Possible values: [BUY, SELL]
BUY or SELL
Possible values: [POST_ONLY, REDUCE_ONLY, SMART_POST_ONLY]
Execution instructions.
Quantity specified in the order.
Limit price specified in the order.
Order value.
Average price.
Cumulative executed quantity.
Cumulative executed value.
Cumulative executed fee.
Possible values: [PENDING, NEW, ACTIVE, FILLED, CANCELED, REJECTED, EXPIRED]
Order status
Updated user.
Order creation date.
E.g. BTCUSD-PERP.
Currency used for the fees.
Order creation timestamp (ms), e.g. "1771761038000".
Order creation timestamp (nanosecond), e.g. "1771761038000000000".
Order update timestamp (ms), e.g. "1771761038000".
Rejection reason code; present for get-order-detail and get-order-history.
Trigger reference price (trigger legs only).
Possible values: [MARK_PRICE, INDEX_PRICE, LAST_PRICE]
Price source used for ref_price: MARK_PRICE, INDEX_PRICE, or LAST_PRICE (trigger legs only).
Transaction timestamp in nanoseconds.