Market WebSocket

Use Market WebSocket when your app needs one hosted market socket for live price updates, rolling short-range OHLCV candles, and explicit stream-status signals under the same API key model as the rest of the public product.

This is the product-level stream surface. Use raw RPC WebSocket only when you need native chain subscriptions.

Access

Endpoint: wss://gw-aql.tomo.services/v1/market/ws
Auth: Authorization: Bearer <api_key>
Surfaces: ws
Chain focus: EVM family primary · Solana (Beta)

Highlights

One hosted WebSocket connection for live price, OHLCV, and stream-status updates.
Use Authorization: Bearer <api_key> during connection setup and subscription access.
Public examples default to the EVM family, while Solana stays on the separate Beta lane.
Connection, price, OHLCV, and stream-status pages now live under this family.

How to use the stream tree

Connect once

Open the hosted websocket endpoint and send the bearer header during upgrade.

Start with one price target

Confirm the first MARKET_PRICE event before widening into more targets.

Handle status events early

Wire explicit status events before production rollout so retry and fallback paths are visible from day one.

Child pages

Open the endpoint, pass bearer auth, and send the first subscribe frame.

Review the MARKET_PRICE event envelope and payload.

Review the rolling candle payload for short_range_ohlcv targets.

Handle continuity gaps, backpressure overflow, and source changes.

Where to start

Start from the simplest public integration flow.

Call Market WebSocket

Return to the shared Market family before drilling into one stream path.

Market overview

Review the product-level stream overview before opening child pages.

Market WebSocket overview

Prepare the bearer token before opening the socket.

Last updated on April 24, 2026