Skip to main content

Endpoint

Connection flow

1. Connect

Open a WebSocket connection. No authentication is needed at connection time.

2. Subscribe

Send a subscribe message within 30 seconds of connecting:

3. Confirmation

On success, the server responds with:

4. Receive broadcasts

Data updates arrive as broadcast messages with both current and previous state:
The old field contains the previous state, making it easy to detect what changed.

5. Keep alive

Send a ping to keep the connection alive:
Server responds with:
The server also sends heartbeats every 60 seconds:

6. Unsubscribe

To stop receiving updates and clean up your subscription:

Channels

Client-filtered channels

These channels only deliver data belonging to your client:

Global channels

All subscribers receive these:

Payload examples

Order fill

When an exchange order gets matched:

Hedge bet placed

After an order fills, the system automatically places a hedge bet:

Live score update

Emergency status

Connection limits

Error messages

Example: Python client

Example: JavaScript client