POST https://api.hyperliquid.xyz/info. The request body, the response shape, and the JSON keys are byte-for-byte identical to the public Hyperliquid API. The only differences are the URL and the authentication header.
Forty-nine wire-compatible type values are supported today across market metadata, user state, user history, vaults, and staking - plus four GoldRush-native types (two batched state lookups and two builder-keyed fill feeds) with no upstream equivalent.
Endpoint
The most-requested reads
Most Hyperliquid apps start from the same REST calls - a user’s trades and their account state. Over the drop-in/info API that is:
- User trades (fills) -
userFillsfor the latest fills, oruserFillsByTimefor a time window (GoldRush serves these past upstream’s ~10,000-fill retention limit). - Perp account state -
clearinghouseStatefor a single wallet, orbatchClearinghouseStatefor up to 50 wallets in one request. - Spot balances -
spotClearinghouseState, orbatchSpotClearinghouseStatefor many wallets at once.
POST /info with a type field - so these are the same requests you already make against api.hyperliquid.xyz, pointed at a faster, unthrottled host.
Comparison with the public Hyperliquid API
Available types
The Info API supports the wire-compatible drop-in types below, organized by what they return. Four GoldRush-native types (batchClearinghouseState, batchSpotClearinghouseState, builderFills, builderFillsByTime) have no upstream Hyperliquid equivalent.
Market metadata
User account state
User history
Vaults & staking
Builder activity
GoldRush-native batch
If you send a
type that isn’t in the table above, the response body is {"error":"unsupported_type","type":"<the type you sent>"}. Requests are not forwarded to upstream Hyperliquid.
How clients see it
Existing Hyperliquid SDKs work unchanged after abaseUrl override. See SDK compatibility for nomeida/hyperliquid (JS) and hyperliquid-dex/hyperliquid-python-sdk setup snippets.
Errors
Networks
Mainnet only. Testnet support is deferred.Next
Migration guide
Side-by-side examples - change one URL and one header.
SDK compatibility
Drop-in setup for
nomeida/hyperliquid and hyperliquid-python-sdk.Limits and caching
No rate limits - what to know about caching and recommended polling cadences.
API reference
Per-endpoint request and response schemas.