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

userAssetData

ChanneluserAssetDataserver → client · type userAssetData

Same as activeAssetData, for every instrument in one subscription.

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

User to follow. Use the account address, not an agent's.

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
"userAssetData"
dataWsUserAssetData
coinsWsUserSingleAssetData[]
userstring
Message example
{
  "channel": "userAssetData",
  "data": {
    "user": "0x0000000000000000000000000000000000000000",
    "coins": [
      {
        "coin": "4",
        "leverage": {
          "type": "Cross",
          "value": 0,
          "rawUsd": ""
        },
        "maxTradeSzs": [
          ""
        ],
        "availableToTrade": [
          ""
        ],
        "markPx": "0",
        "onlyIsolated": false
      }
    ]
  }
}