Connecting to Futures WebSockets
Public market-data sockets for futures use Socket.IO v4 with a single namespace per exchange.
Connection details
| Type | Socket.IO |
| Version | v4 |
| Base URL | wss://ws.coinswitch.co/ |
| Handshake path | /pro/realtime-rates-socket/futures/{exchange} |
{exchange} in the handshake path is exchange_2 (lowercase).
Namespace
| Exchange | Namespace |
|---|---|
EXCHANGE_2 | /exchange_2 (lowercase in the namespace) |
Subscription protocol
Each event (Order Book, Ticker, Trades, KLines) follows the same shape:
- Connect to the namespace.
emitthe event name with asubscribepayload that includes the symbol you care about.- The server pushes updates back on the same event name.
Symbol convention
Most futures WebSocket events use the same BASEUSDT format as REST (e.g. BTCUSDT).
The KLines event is special — it uses SYMBOL_INTERVAL (e.g. BTCUSDT_5 for 5-minute candles). See the KLines page for details.
Authentication
Public market-data sockets are unauthenticated — anyone with the URL can subscribe.
User-data sockets (Order updates, Position updates) aren't available on Futures today.
Next
- Order Book — real-time depth snapshots
- Ticker — last price + funding + open-interest pushes
- Trades — real-time trade prints
- KLines — real-time candles, with the special
SYMBOL_INTERVALsubscription pattern