`outcomeOrderUpdates`

Streams matching-engine lifecycle updates for one user's Outcome orders over the node /ws connection.

ChanneloutcomeOrderUpdatesserver → client · type outcomeOrderUpdates

Track the matching lifecycle of a user’s Outcome orders: filled, rejected, cancelled.

{
  "method": "subscribe",
  "type": "outcomeOrderUpdates",
  "subscription": {
    "type": "outcomeOrderUpdates",
    "user": "0xabc123abc123abc123abc123abc123abc123abc1",
    "instrumentIds": [
      9001
    ]
  }
}

Try it

WS wss://rpc.txflow-testnet.xyz/ws

Subscription parameters

typestringrequired

"outcomeOrderUpdates"

userstring · addressrequired

instrumentIdsinteger · uint64[]optional

Optional filter. Omit or send an empty list for all Outcome instruments.

Server message

channelstring

"outcomeOrderUpdates"

dataobject[]

orderobject

statusstring

statusTimestampinteger · int64

Message example

{
  "channel": "outcomeOrderUpdates",
  "data": [
    {
      "order": {
        "asset": 1000001,
        "coin": "OUTCOME-1000001",
        "side": "B",
        "orderType": "Market",
        "limitPx": "0.550",
        "sz": "0",
        "origSz": "10",
        "avgFillPrice": "0.549",
        "oid": 179297706115,
        "timestamp": 1700000000000,
        "reduceOnly": false,
        "outcome": "Yes",
        "isTrigger": false
      },
      "status": "Filled",
      "statusTimestamp": 1700000000000
    }
  ]
}

Omit instrumentIds, or send an empty list, to follow every Outcome market for the user. When present, the list filters the stream to those instruments.

The outcome field is the displayed leg (Yes or No); side remains the underlying YES-book side (B or A). Use this channel for filled, rejected, and canceled lifecycle events. The separate outcomeOrderUpdate channel reports orders that fail in the gateway's asynchronous acceptance path.