Endpoint
Connection flow
1. Connect
Open a WebSocket connection. No authentication is needed at connection time.2. Login
Send a login message within 30 seconds of connecting:channels array subscribes to all available channels. To subscribe to specific channels:
3. Login confirmation
On success, the server responds with:4. Receive updates
Data messages follow this format:| Field | Description |
|---|---|
type | Always "data" for data messages |
channel | Which channel this message belongs to |
event | Event type: INSERT, UPDATE, DELETE, STATUS_CHANGE, SETTLED |
payload | The full updated object |
ts | Server timestamp (milliseconds since epoch) |
seq | Sequence number for message ordering |
5. Keep alive
Send a ping every 30 seconds:Channels
Client-filtered channels
These channels only deliver data belonging to yourclientName:
| Channel | Events | Description |
|---|---|---|
orders | INSERT, UPDATE, STATUS_CHANGE | Order placement, fills, status changes |
bets | INSERT, UPDATE, SETTLED | Bet placement, confirmation, settlement |
settlements | UPDATE | Settlement status updates |
accounts | UPDATE | Account balance and status changes |
balance | UPDATE | Balance change notifications |
Global channels
All subscribers receive these:| Channel | Events | Description |
|---|---|---|
fixtures | UPDATE | Fixture metadata and score changes |
currencies | UPDATE | Currency exchange rate updates |
status | UPDATE | System status changes |
emergency | UPDATE | Emergency mode activation/deactivation |
Payload examples
Order update
Bet confirmation
Bet settlement
Connection limits
| Setting | Value |
|---|---|
| Max connections per API key | 5 |
| Auth timeout | 30 seconds |
| Server heartbeat interval | 60 seconds |
| Client ping interval | 30 seconds (recommended) |
| Message buffer size | 100 per subscription |