{
"type": "subscribe",
"channel": "account",
"id": "0xAbCd...1234"
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"market": "<string>",
"contents": {}
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"market": "<string>",
"contents": {}
}User fills
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-user fill stream. Snapshot on subscribe contains recent fills; streaming updates deliver each new fill as orders are matched. Snapshot is sent once on connect only.
LIQUIDATION and ADL fills also appear here carrying the liquidation marker (method + liquidatedUser) — on the liquidated account’s leg for LIQUIDATION and the deleveraged counterparty’s leg for ADL — so subscribers tracking realized closures can observe forced fills on either account or userFills. The marker is persisted, so it is present in snapshots as well as live updates.
Optionally scoped to one market: pass market on subscribe (ticker or numeric id) and the snapshot, the live frames, and the post-snapshot catch-up all carry only that market. The filter is part of subscription identity, so one connection can hold several market-scoped views of the same account; unsubscribe must repeat the same market.
{
"type": "subscribe",
"channel": "account",
"id": "0xAbCd...1234"
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"market": "<string>",
"contents": {}
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"market": "<string>",
"contents": {}
}Recent fills sent once on subscribe.
One fill per frame as orders are matched.
Was this page helpful?