{
"type": "subscribe",
"channel": "account",
"id": "0xAbCd...1234"
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"throttleMs": 123,
"market": "<string>",
"contents": {}
}Settle loan results
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 settleLoan request outcomes — the engine’s ack for every POST /v1/settleLoan, APPLIED and REJECTED alike, one frame per request. The WS twin of the REST response body (same fields and display units), correlatable with the REST 202 ACK by requestId. This is the only WebSocket surface for settleLoan rejections: a reject moves no cash and produces no fill or state frame. An APPLIED settlement is additionally visible on spotFills as a LOAN_SETTLE fill, but only this channel carries the requestId correlation and the loan math (repaidAmount / newLoanBalance).
Stream-only: no snapshot on subscribe (the trades precedent) — the subscribe ack carries empty contents ({}) and frames flow from the moment of subscription.
{
"type": "subscribe",
"channel": "account",
"id": "0xAbCd...1234"
}{
"type": "<string>",
"channel": "<string>",
"id": "<string>",
"accountIndex": 123,
"sigFigs": 123,
"roundStep": 123,
"throttleMs": 123,
"market": "<string>",
"contents": {}
}One engine-confirmed settleLoan outcome per frame (APPLIED or REJECTED), mirroring the POST /v1/settleLoan response body. See the openapi SettleLoanResultMessage schema.
Was this page helpful?