Skip to main content
Protocol messages handle connection lifecycle, identity verification, session management, and balance queries. They do not carry gameType or tableId.

Message Reference

hello

Direction: Server → Client (immediately after WebSocket connection)
The server MUST send hello before any other message. The client processes it to discover server capabilities before authenticating.

authenticate

Direction: Client → Server (first message after receiving hello)
Tokens MUST NOT be passed in the WebSocket URL query string. Servers MUST close connections that do not authenticate within 10 seconds of receiving hello.

authenticated

Direction: Server → Client
The response includes the linked user context and the client’s granted permissions. Servers MUST enforce these permissions for all subsequent actions.

balance_query / balance_response

Direction: Client → Server / Server → Client
Clients MAY query their balance at any time during an authenticated session.

session_extend / session_extended

Direction: Client → Server / Server → Client

session_expiring

Direction: Server → Client
Servers MUST send this at least 5 minutes before session expiry. Servers SHOULD also send it before applying the inactivity timeout.

heartbeat

Direction: Bidirectional

error

Direction: Server → Client
See Error Codes for the complete code catalog.