Feeds / Crypto exchanges (live)

Binance.US

Spot. WebSocket diffs, seeded by a REST snapshot; diffs that arrive before the snapshot are buffered and replayed afterwards.

Live in productionWebSocketFull-depth diffs; REST snapshot of 1,000 levels

Live now

-
books live
-
messages / s
-
level changes / s
-
KB / s

Messages / s and KB / s are what our handler receives from the exchange (KB after decompression, REST snapshots included); level changes / s are counted after normalization, for the markets we publish.

Open live books Replay

How we connect

Market
Spot
WebSocket
wss://stream.binance.us:9443/ws
Channels
<symbol>@depth — diff depth, 1000 ms
<symbol>@trade — trades, real time
Update model
WebSocket diffs, seeded by a REST snapshot; diffs that arrive before the snapshot are buffered and replayed afterwards.
Snapshot (REST)
https://api.binance.us/api/v3/depth?symbol={SYMBOL}&limit=1000
Sequencing
Each diff carries U (first update ID) and u (final update ID). Buffered diffs with u <= the snapshot's lastUpdateId are dropped; live diffs with u <= the last applied ID are ignored; a diff is a gap if U > last applied u + 1.
On a gap
Only that symbol is marked unsynced: its buffer is cleared, the diff that broke the sequence is kept, a fresh REST snapshot is fetched for it and the buffered diffs are replayed - the connection stays up. On a socket error or 30 s without data we reconnect (5 s backoff, doubling) and re-fetch every snapshot.
Depth
Full-depth diffs; REST snapshot of 1,000 levels
Authentication
none
Heartbeat
We answer the server's WebSocket pings; a 30 s no-data watchdog forces a reconnect.
Symbol format
BTCUSDT (stream names lowercase: btcusdt@depth)

Subscribe message

{"method":"SUBSCRIBE","params":["btcusdt@depth","btcusdt@trade","ethusdt@depth","ethusdt@trade",...],"id":1}

What our handler takes care of

Instruments

loading...

Upcoming and recent changes

2026-10-28InfoSBE documented; schema 3:3 retired 11/9/2026effective 2026-11-09May affect market data
A Simple Binary Encoding section was added. SBE schema 3:5 is current; 3:2, 3:3 and 3:4 are deprecated, and 3:3 will be retired on 2026-11-09.
Details

SBE responses were already available on the REST API without documentation. Requests for a retired schema are rejected. Retirement dates for 3:2 and 3:4 will be announced later. Our handler uses JSON, so no action is needed unless SBE is requested on the depth snapshot.

Our handler: Only matters if SBE responses are requested from the REST /api/v3/depth snapshot; the handler appears to use JSON.

Source ↗

2026-10-26InfoSelf-generated API keys (Ed25519/RSA)
API keys can now be self-generated with Ed25519 or RSA key pairs and used for signing requests.
Details

Existing HMAC keys are unchanged. This applies to authenticated endpoints only. Our handler uses no authentication, so nothing needs to change.

Our handler: Authentication change for signed endpoints; our market data handler uses no auth.

Source ↗

2026-10-06InfoAlternative REST base endpoints api1 and api2May affect market data
https://api1.binance.us and https://api2.binance.us are now available, identical to api.binance.us in functionality and rate limits.
Details

They may offer better performance as requests pass through fewer infrastructure layers. Optionally use them as fallback hosts for the depth snapshot request if the base endpoint has issues. No action is required.

Our handler: Alternative hosts for the REST snapshot at api.binance.us/api/v3/depth that could serve as fallbacks.

Source ↗

2026-09-17InfolistenKey User Data Streams deprecated; sunset targeted Q4 2026
The listenKey-based User Data Stream, including listenKey connections to wss://stream.binance.us:9443, will be retired on a date to be announced, targeted for Q4 2026.
Details

Affected are POST/PUT/DELETE /api/v3/userDataStream and the WebSocket API userDataStream.start/ping/stop methods. A new userDataStream.subscribe.signature method was added to the WebSocket API. This concerns account data only, and our public streams are not affected.

Our handler: Only user data streams are affected; our depth and trade streams are public.

Source ↗

2026-09-01BreakingRemoval of buyer/seller order ID fields from <symbol>@tradeeffective 2026-08-31Affects our handler
The buyer order ID and seller order ID fields were removed from the <symbol>@trade stream payload as part of the 8/31/2026 upgrade.
Details

Any parser that reads the buyer order ID (b) or seller order ID (a) fields from trade messages must stop depending on them. Update the trade message schema and make parsing tolerant of their absence.

Our handler: The <symbol>@trade channel payload we consume no longer contains the buyer and seller order ID fields.

Source ↗

2026-09-01Action neededLocal order book guide updated; snapshot limit up to 5000effective 2026-08-31Affects our handler
The documented steps for managing a local order book were updated, with depth snapshots now referencing up to 5000 levels per side and clearer buffering and sync steps.
Details

Review the handler's snapshot-and-diff synchronization against the updated procedure. A limit of 5000 is now documented for the snapshot, whereas we use 1000.

Our handler: Affects the @depth diff stream and the REST /api/v3/depth snapshot synchronization procedure we use.

Source ↗

Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed

Official documentation

Binance.US API — Order Book Depth Diff Stream ↗docs.binance.usBinance.US API — Managing a Local Order Book ↗docs.binance.usBinance.US API — Get Order Book Depth (REST) ↗docs.binance.usBinance.US API — Rate limits ↗docs.binance.usBinance.US API — Changelog ↗docs.binance.usSystem status ↗www.binance.us

Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.