Skip to Content
Call RPC WebSocket

Call RPC WebSocket

Hosted RPC WebSocket keeps native chain subscriptions separate from the market stream surface. The current gateway baseline exposes the EVM websocket family, plus a separate Solana WebSocket route (Beta). Send Authorization: Bearer <api_key> during the WebSocket upgrade before the first reviewed subscription call.

Raw RPC WebSocket follows the same chain-family split as raw RPC. Open /services/evm or /services/solana when you need the reviewed subscription reference pages.

Access

  • EVM routes: wss://gw-aql.tomo.services/rpc/ethereum/wss, wss://gw-aql.tomo.services/rpc/bnbchain/wss, wss://gw-aql.tomo.services/rpc/base/wss
  • Solana route (Beta): wss://gw-aql.tomo.services/rpc/solana/wss
  • Auth: Authorization: Bearer <api_key>

How to call RPC WebSocket

Create one API key

Open Get API Key and keep the bearer token ready.

Pick one chain-family websocket route

Choose one EVM websocket route by default, or use the Solana WebSocket route (Beta) only when you need the separate Beta lane.

Start with one reviewed topic

Use a reviewed subscription topic first, then widen into more native chain listeners only after the first stream is stable.

Connection examples

wscat -c "wss://gw-aql.tomo.services/rpc/ethereum/wss" \ -H "Authorization: Bearer <api_key>"
{ "jsonrpc": "2.0", "id": 1, "method": "eth_subscribe", "params": ["newHeads"] }

Open one chain-family menu

Last updated on