The most popular Hyperliquid SDKs work against the GoldRush WebSocket API after a one-line URL override. Authentication is aDocumentation Index
Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
key query parameter on the connection URL - no header injection is needed.
JavaScript / TypeScript: nomeida/hyperliquid
Install
Configure
If your SDK version doesn’t expose a
wsUrl option, instantiate the WebSocket client manually and pass it to the SDK, or patch the constant the SDK uses. See the override fallback below.Manual WebSocket fallback
When the SDK doesn’t expose awsUrl knob, bypass it and drive the raw socket yourself:
Python: hyperliquid-dex/hyperliquid-python-sdk
Install
Configure
Verification
After cutover, confirm everything is wired correctly:- Diff a known subscription - subscribe to
l2Bookfor the same coin against both endpoints; the streamedchannelanddatashape (keys, nesting, types) should match exactly. - Confirm auth - remove the
keyquery parameter and confirm the WebSocket upgrade fails with HTTP401. If the socket opens, your request isn’t reaching GoldRush. - Confirm wildcard - subscribe to
l2Bookwithout acoinand confirm you receive book snapshots for multiple assets. This call would be rejected on the public Hyperliquid WebSocket.
Other SDKs
The pattern is the same for any WebSocket client: override the connection URL towss://hypercore.goldrushdata.com/ws?key=<GOLDRUSH_API_KEY>. If you run into a specific SDK that doesn’t expose a URL override, email us - we’ll publish a recipe.