WebSocket Connected but No Data

To isolate whether the issue lies in your WebSocket plumbing or the target stock’s trading session, temporarily subscribe to a highly liquid 24/5 FX pair such as EURUSD on quote-b-ws-api. Receiving ticks confirms your auth and subscription flow are healthy.

1import asyncio, json, os, uuid
2import websockets
3
4async def probe():
5    token = os.getenv("ALLTICK_API_TOKEN", "YOUR_API_TOKEN")
6    url = f"wss://quote.alltick.co/quote-b-ws-api?token={token}"
7    async with websockets.connect(url) as ws:
8        await ws.send(json.dumps({
9            "cmd_id": 22004,
10            "seq_id": 1,
11            "trace": str(uuid.uuid4()),
12            "data": {"symbol_list": [{"code": "EURUSD"}]},
13        }))
14        for _ in range(5):
15            print(await asyncio.wait_for(ws.recv(), timeout=30))
16
17if __name__ == "__main__":
18    asyncio.run(probe())

WebSocket servers do not carry over subscriptions from dropped connections. If your client only sends the subscription message once at startup, any subsequent reconnect will result in an idle connection with zero push messages. Always place the subscribe call inside your connection handler.

• WebSocket endpoint URL (with token redacted) and exact JSON subscription payload.
• All raw frames received immediately after connecting and subscribing.
• UTC timestamp and duration of the incident.
• Programming language, WebSocket library name, and version.