{
"type": "subscribe",
"channel": "l2OrderbookUpdates",
"id": "BTC-USD",
"nLevels": 50
}{
"type": "subscribed",
"channel": "l2Orderbook",
"id": "BTC-USD",
"contents": {
"bids": [
[
"94500.0",
"1.5"
],
[
"94499.0",
"2.0"
]
],
"asks": [
[
"94501.0",
"0.8"
],
[
"94502.0",
"3.1"
]
],
"lastSequenceId": 1042,
"globalSequenceId": 880421,
"timestamp": 1780410803123456
}
}{
"type": "channel_data",
"channel": "l2OrderbookUpdates",
"id": "BTC-USD",
"contents": {
"bids": [
[
"94499.0",
"0"
]
],
"asks": [
[
"94503.0",
"1.2"
]
],
"timestamp": 1780410803124012,
"lastSequenceId": 1043,
"globalSequenceId": 880422
}
}L2 orderbook 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.
Full L2 orderbook snapshot followed by event-driven incremental deltas for a single market.
On subscribe: full snapshot up to nLevels per side, then delta updates as orders are placed, modified, or cancelled. Each delta carries a monotonically increasing per-market lastSequenceId.
Reconciliation: Deltas carry absolute level sizes and lastSequenceId increases by exactly 1 per delta, so a skipped delta is never repaired by later ones. The subscribe snapshot can lag the stream, so the first delta may be more than 1 past it — treat that like any other gap and re-seed as described in the WebSocket guide. A single delta frame may list the same price more than once; apply entries in array order, last-write-wins per price.
{
"type": "subscribe",
"channel": "l2OrderbookUpdates",
"id": "BTC-USD",
"nLevels": 50
}{
"type": "subscribed",
"channel": "l2Orderbook",
"id": "BTC-USD",
"contents": {
"bids": [
[
"94500.0",
"1.5"
],
[
"94499.0",
"2.0"
]
],
"asks": [
[
"94501.0",
"0.8"
],
[
"94502.0",
"3.1"
]
],
"lastSequenceId": 1042,
"globalSequenceId": 880421,
"timestamp": 1780410803123456
}
}{
"type": "channel_data",
"channel": "l2OrderbookUpdates",
"id": "BTC-USD",
"contents": {
"bids": [
[
"94499.0",
"0"
]
],
"asks": [
[
"94503.0",
"1.2"
]
],
"timestamp": 1780410803124012,
"lastSequenceId": 1043,
"globalSequenceId": 880422
}
}size: "0" means the level was removed. Deltas carry absolute level sizes and lastSequenceId increases by exactly 1 per delta, so a skipped delta is never repaired by later ones. The subscribe snapshot can lag the stream, so the first delta may be more than 1 past it — treat that like any other gap and re-seed as described in the WebSocket guide.
Was this page helpful?