Future Websocket Endpoint Changed

sittikom

[https://developers.binance.com/docs/derivatives/usds-margined-futures/websocket-market-streams](https://developers.binance.com/docs/derivatives/usds-margined-futures/websocket-market-streams) has **/market** Websocket Market Streams The connection method for Websocket is： Base Url: wss://fstream.binance.com Three routed endpoints are available based on data type: Public (high-frequency public market data): wss://fstream.binance.com/public Market (regular market data): wss://fstream.binance.com/market Private (user data): wss://fstream.binance.com/private Two access modes are supported: ws mode: streams are composed in the URL path — /ws/<streamName> stream mode: streams are passed via query parameters — /stream?streams=<streamName1>/<streamName2>/<streamName3> Examples: wss://fstream.binance.com/market/ws/bnbusdt@aggTrade wss://fstream.binance.com/public/ws/bnbusdt@depth/ethusdt@depth wss://fstream.binance.com/market/stream?streams=bnbusdt@aggTrade/btcusdt@markPrice

pcriadoperez

Thanks for the message @sittikom , I'll look into this

pcriadoperez

Hi @sittikom , after checking. The library already migrated to the /public /market /private endpoints — update to node-binance-api ≥ 1.0.27 and futures streams route automatically; no code changes needed. The only caveat: don't mix public streams (@depth/@bookTicker) and market streams (@aggTrade/@markPrice/kline/etc.) in a single futuresSubscribe([...]) call — use separate subscriptions, which is also Binance's recommendation.

pcriadoperez

I'll close the issue for now but feel free to reach out with any questions