Skip to main content
Authorize the WebSocket connection for private channel access. Send a WebSocket token obtained from the REST API. This channel handles WebSocket connection authorization. Authorize once per connection — all private channels become accessible after a single successful authorization.
Connect to wss://api.whitebit.com/ws — see WebSocket Overview for protocol details and keepalive requirements.

​
Rate limits

​
Authorization flow

Step 1 — Get a WebSocket token Call the REST endpoint to obtain a short-lived token: 
POST /api/v4/profile/websocket_token
See WebSocket Authentication for the full flow including request signing. Step 2 — Send authorization request Step 3 — Receive confirmation The connection is authorized. Subscribe to any private channel on the same connection.
Authorization is per connection, not per subscription. Authorize once, then subscribe to as many private channels as needed on the same WebSocket connection.

​
Update frequency

Client-initiated. Send an authorize request after each new WebSocket connection.

​
Error codes