{
"type": "subscribe",
"channel": "account",
"id": "0xAbCd...1234"
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"throttleMs": 123,
"market": "<string>",
"contents": {}
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"throttleMs": 123,
"market": "<string>",
"contents": {}
}Spot 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 spot fill stream — the seizure and loan-settle executions of the lending system. Spot has no orderbook, so these are the only spot executions and there is no maker/taker role or fee. Snapshot on subscribe contains recent spot fills from the store; streaming updates deliver each new spot fill as it is executed. Snapshot is sent once on connect only; subscribe with snapshot: false to skip it and receive only live spot fills (use REST /v1/spotFills for history).
For settleLoan request outcomes (including rejections, which produce no fill), see the settleLoanResults channel.
{
"type": "subscribe",
"channel": "account",
"id": "0xAbCd...1234"
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"throttleMs": 123,
"market": "<string>",
"contents": {}
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"throttleMs": 123,
"market": "<string>",
"contents": {}
}Recent spot fills (seizure / loan-settle) sent once on subscribe.
One spot fill per frame as seizure / loan-settle executions occur.
Was this page helpful?