{
"type": "subscribe",
"channel": "account",
"id": "0xAbCd...1234"
}{}{}Account attribute updates
Endpoint:
wss://api.arcus.xyz/v1/ws— one socket multiplexes every channel and RPC request. Click Connect, then send the example subscribe message below to start receiving data.
Per-account attribute state, discriminated by entry type. type: "leverage" entries carry effective leverage and margin mode per market. isolated and marginMode are always present — in the snapshot they reflect the current persisted state; in streaming frames they reflect the account’s margin mode after the triggering event, defaulting to CROSS if the margin mode lookup fails. type: "feeTier" entries carry account-level fee tier state. type: "leverageReject" entries (streaming only) report that a setLeverage request was refused by the engine — this is the REJECTED half of the setLeverage lifecycle; an applied change arrives as a leverage entry. When isolated was also supplied on the request, both the leverage and margin mode outcomes are folded into the same entry via the optional marginModeStatus and marginModeRejectReason fields. Snapshot returns one leverage entry per market (carrying both leverage and margin mode state) plus, when available, one fee tier entry. Streaming delivers one entry for each changed attribute.
{
"type": "subscribe",
"channel": "account",
"id": "0xAbCd...1234"
}{}{}One leverage entry per market (carrying both leverage and margin mode state), plus one fee tier entry when available. Sent once on subscribe.
Single-entry delta keyed by type. A leverage or feeTier entry is a state change; a leverageReject entry reports a refused request (no state change). When isolated was part of a setLeverage request the margin mode outcome is carried inside the same entry.
Was this page helpful?