hyperliquid-websocket

Send a subscribe message with subscription type userFills and your account address, or call info.subscribe({"type": "userFills", "user": address}, callback) with the Python SDK. The first message is a snapshot with isSnapshot true; only later messages are new fills.

Supported types include allMids, l2Book, trades, candle, bbo, activeAssetCtx, userFills, orderUpdates, userEvents, userFundings, activeAssetData, clearinghouseState, openOrders, twapStates, and webData3. Each takes a JSON subscription object with fields like coin, user, or interval.

No, the official Python SDK pings automatically but does not reconnect on drop. Run the watch under a supervisor, log a heartbeat, and restart the process if the log goes stale for more than a few minutes.

The Python SDK only routes certain subscription types to callbacks; types like clearinghouseState, openOrders, twapStates, and webData3 are acknowledged by the server but silently dropped by the SDK. Use the raw socket or the TypeScript client for those.

Limits are up to 10 connections, 30 new connections per minute, 1000 subscriptions, 10 distinct users across user subscriptions, and 2000 messages per minute. The server closes any connection silent for 60 seconds, so send pings or expect activity within that window.

Yes, all WebSocket subscriptions are read-only and require no key or signature. Account streams like userFills and orderUpdates only need the public account address, and the skill never calls the /exchange endpoint.