Websocket Introduction

Access

The base URL of Websocket Market Data is: wss://ws.azbit.com

Each channel is a path on that host — /orderbooks-snapshots, /orderbooks-changes, /latest-price, /market, /market24, /ping. Connect straight to the channel you want; there is no multiplexing across one socket.

The endpoints accept only a WebSocket upgrade. A plain GET returns 404 — that is the expected answer to a browser or curl probe, not a sign the gateway is down.

Subscriptions

Once connected, subscribe with:

{ "Method": "subscribe", "CurrencyPairs": ["BTC_USDT"] }

Params is accepted as a synonym for CurrencyPairs on every channel, so either spelling works.

The server confirms with:

{ "Result": "Subscribed" }

After that, every update to the subscribed data is pushed to the client.

Unsubscribe

{ "Method": "unsubscribe", "CurrencyPairs": ["BTC_USDT"] }

Confirmation:

{ "Result": "Unsubscribed" }

Keeping the connection alive

The server sends a WebSocket ping every 120 seconds; answer with the standard pong (every mainstream client library does this for you). The /ping channel exists for clients that want to probe liveness explicitly.

Orders are not cancelled when a connection drops — the socket carries market data only, and it has no bearing on your open orders. There is no cancel-on-disconnect option.