Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

orderUpdates

ChannelorderUpdatesserver → client · type orderUpdates

Track a user’s orders live: placed, filled, cancelled, rejected.

Subscribe
{
  "method": "subscribe",
  "type": "orderUpdates",
  "subscription": {
    "type": "orderUpdates",
    "user": "0x0000000000000000000000000000000000000000",
    "coin": "4"
  }
}
Try it
WS wss://rpc.txflow-testnet.xyz/ws
Subscription parameters
typestringrequired
"orderUpdates"
userEthAddressrequired

User whose orders to track. Use the account address, not an agent's.

coinstringoptional

Optional trading-pair filter. Omitted or "" means all coins.

exchangeIdExchangeScopeoptional

Filter by an instrument's configured exchange_id. Same three-state semantics as the HTTP /info ExchangeScope: missing, null, or 0 -> Default (only instruments with no configured exchange_id); the string "all" (case-insensitive) -> All (no filter, every exchange); a positive integer n -> Exchange(n) (only that exchange_id).

oneOf · variant 1
null
oneOf · variant 2
integer
oneOf · variant 3
string
Server message
channelstring
"orderUpdates"
dataWsOrderUpdate[]
orderWsBasicOrder
statusstring

Order lifecycle status.

"Pending""Open""PartialFilled""Filled""PartialCanceled""Canceled""Rejected"
statusTimestampinteger

Timestamp of this status change, milliseconds.

Message example
{
  "channel": "orderUpdates",
  "data": [
    {
      "order": {
        "asset": 1,
        "coin": "BTC-USDC",
        "side": "B",
        "orderType": "Limit",
        "limitPx": "83000.0",
        "sz": "0.001",
        "oid": 123456,
        "timestamp": 1700000000000,
        "origSz": "0.001",
        "avgFillPrice": null,
        "reduceOnly": false,
        "isTrigger": false
      },
      "status": "Pending",
      "statusTimestamp": 1700000000000
    }
  ]
}