Skip to main content
Murmo exposes two real-time gateways over Socket.IO. Both accept your murmo_ API key, so a bot can stream live data without polling.

Connecting

Pass your key in the Socket.IO handshake auth.token. It may also be sent as an Authorization: Bearer header. It is never read from the query string (query strings leak into logs).

Connection lifecycle

1

Connect with your key

On success the server emits connected. For /chat it also auto-joins you to all your group rooms and a private user:{userId} room.
2

Subscribe to what you need

On /perps, emit subscribe_market { symbol } per market. On /chat, you already receive your groups’ messages after connecting.
3

Handle `error` and reconnects

Auth failures emit error then disconnect. Socket.IO reconnects automatically; re-subscribe on reconnect.
An invalid or missing token emits error (Authentication required / Invalid token) and the socket is disconnected. Make sure auth.token is your murmo_ key.

Which gateway to use

Market data

/perps — subscribe per symbol, receive throttled market_tick pushes.

Chat & notifications

/chat — messages, reactions, pins, and per-user notifications.
Need exact decimal prices (the REST money-string contract)? Read GET /api/v1/perps/markets. The market_tick stream optimizes for latency and sends numeric fields (see the next page).