Market Trading Updates - Notional Protocol

Hyperliquid

Streams leverage, mark price, estimated buy/sell capacity, and isolated-market permissions for one user and perpetual market. An initial frame has isSnapshot: true; subsequent updates have isSnapshot: false. For a one-time HTTP read, use Market Trading State.

{
  "method": "subscribe",
  "subscription": {
    "type": "activeAssetData",
    "user": "0x1111111111111111111111111111111111111111",
    "coin": "BTC"
  }
}

Response

{
  "channel": "activeAssetData",
  "data": {
    "user": "0x1111111111111111111111111111111111111111",
    "coin": "BTC",
    "leverage": {
      "type": "cross",
      "value": 5
    },
    "maxTradeSzs": ["0.1", "0.1"],
    "availableToTrade": ["1000.00", "1000.00"],
    "markPx": "50000",
    "isSnapshot": true
  }
}

Fields

data has the Market Trading State response fields plus the WebSocket-only isSnapshot flag. Array order is [buy, sell] for both maxTradeSzs and availableToTrade.

Assigned HIP-3 Markets

Send the qualified perpetual venueName, such as "idx:IDX0", as coin. Assigned markets include leverage.type: "isolated" and the isolated state: leverage selection, permissions, scope balances, and any live operation. A pending target is not confirmed leverage. Read the permission for each action before submitting it.

Snapshot Failures

The subscription is acknowledged before its snapshot is loaded. If the market, mark price, margin pricing, or account state is unavailable, the server sends an error message instead of a usable snapshot. Keep the last state marked stale and retry the HTTP snapshot; do not interpret the acknowledgment as current data.