Skip to main content

Documentation Index

Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

GoldRush Hyperliquid API

The complete data layer for Hyperliquid. One API key unlocks:
  • Info API - drop-in replacement for POST api.hyperliquid.xyz/info at hypercore.goldrushdata.com/info. No rate limits. Same request body, same response shape.
  • WebSocket API - drop-in replacement for wss://api.hyperliquid.xyz/ws at wss://hypercore.goldrushdata.com/ws?key=<KEY>. No 1000-subscription-per-IP cap. l2Book (wildcard coin) and the GoldRush-native l4Book order-level diff stream.
  • Streaming API - walletTxs for the wallet firehose, ohlcvCandlesForPair/ohlcvCandlesForToken for HIP-3 and HIP-4 OHLCV with deployer-prefix syntax.
  • Pipeline API - hl_fills, hl_trades, hl_orders, hl_funding, hl_misc_events to ClickHouse, BigQuery, Postgres, Kafka, S3.
  • Foundational API - HyperEVM token balances, transfers, approvals, NFTs, gas.

Drop-in Info API

// Before
fetch("https://api.hyperliquid.xyz/info", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ type: "clearinghouseState", user: "0x...", dex: "" }),
});

// After - same body, no rate limits
fetch("https://hypercore.goldrushdata.com/info", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.GOLDRUSH_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ type: "clearinghouseState", user: "0x...", dex: "" }),
});
That’s it. Existing SDKs (nomeida/hyperliquid for JS, hyperliquid-python-sdk for Python) work after a baseUrl override.

Available Info API types (today)

TypeUse
metaAndAssetCtxsPerp universe + per-asset live mark price, funding, OI, day volume
spotMetaAndAssetCtxsSpot universe + per-pair live mark price, mid, day volume
outcomeMetaActive HIP-4 outcome universe with outcome IDs, descriptions, and Yes/No side specs
clearinghouseStatePer-user perp account: positions, margin, account value
spotClearinghouseStatePer-user spot balances
frontendOpenOrdersPer-user open orders with TP/SL trigger metadata
subAccountsSub-accounts owned by a master, each with inlined perp and spot state
userFillsMost recent fills for a user
userFillsByTimeFills bounded by a time window
userTwapSliceFillsMost recent TWAP slice fills tagged with the parent twapId
userFundingFunding payment history with rate, applied size, USDC delta
userNonFundingLedgerUpdatesLedger events except funding - deposits, withdrawals, transfers, vault flows, liquidations
userVaultEquitiesPer-vault locked equity with unlock timestamps
delegatorSummaryCurrent delegated, undelegated, and pending-withdrawal HYPE totals
delegatorHistoryDelegate, undelegate, deposit, and withdrawal staking events
delegatorRewardsAccrued staking rewards (delegation and validator commission)
batchClearinghouseStatePerp account state for 1-50 wallets in one request. GoldRush-native, no upstream equivalent
batchSpotClearinghouseStateSpot balances for 1-50 wallets in one request. GoldRush-native, no upstream equivalent
Any other type value returns {"error":"unsupported_type","type":"<the type you sent>"}. Type expansion is on the roadmap.

Available WebSocket subscriptions (today)

ChannelUse
l2BookAggregated {px, sz, n} order book per tick. coin is optional - omit to stream every asset on one subscription. Drop-in for wss://api.hyperliquid.xyz/ws l2Book, no per-IP cap.
l4BookOrder-level snapshot of every resting order plus per-block diffs (order_statuses + book_diffs). Exposes user, oid, cloid, tif, triggerCondition. coin is required. GoldRush-native, no upstream equivalent.

When to use which surface

NeedUse
Account state, market snapshot, open ordersInfo API (POST /info)
Live order book - aggregated price levels, wildcard across all assetsWebSocket API l2Book on wss://hypercore.goldrushdata.com/ws
Live order book - per-order detail, queue position, per-user flow attributionWebSocket API l4Book (snapshot + per-block diffs, GoldRush-native)
Real-time wallet activity (1 → 10,000 wallets)Streaming API walletTxs
HIP-3 and HIP-4 OHLCV candlesStreaming API ohlcvCandlesForPair with xyz:GOLD-USDC syntax
Pre-decoded liquidations and vault eventsStreaming API walletTxsHypercoreFillTransaction.liquidation, HypercoreLedgerEvent
Land Hyperliquid data in your warehousePipeline API HyperCore normalizer
HyperEVM (chain 999) token balances/transfers/NFTsFoundational API on hyperevm-mainnet

Critical rules

  1. Info API endpoint URL - https://hypercore.goldrushdata.com/info (note: hypercore, not hyperliquid).
  2. Info API auth header - Authorization: Bearer <GOLDRUSH_API_KEY>. Same key as Foundational/Streaming/Pipeline.
  3. WebSocket API endpoint URL - wss://hypercore.goldrushdata.com/ws?key=<GOLDRUSH_API_KEY>. Auth is a ?key= query parameter at connect time; no Authorization header is sent. Same key as the Info API.
  4. Wire-compat with Hyperliquid - Info API request body and WebSocket subscription payloads are byte-for-byte identical to the public Hyperliquid endpoints for implemented types/channels.
  5. l4Book is GoldRush-only - it does not exist on wss://api.hyperliquid.xyz/ws. coin is required; l2Book’s coin is optional (wildcard streams every asset).
  6. HIP-3 and HIP-4 syntax - <deployer>:<symbol>-<quote> for OHLCV pairs (e.g. xyz:GOLD-USDC); plain symbol for OHLCV tokens.
  7. Streaming chain enum - HYPERCORE_MAINNET (SCREAMING_SNAKE_CASE), not hypercore-mainnet.
  8. Historical depth - HyperCore data starts at block 676,607,001 (2025-07-27T01:49:59Z); HyperEVM goes back to genesis.
  9. No rate limits on the Info API, WebSocket API, or Streaming API for HyperCore. No 1000-subscription-per-IP cap on the WebSocket API.

Reference Files

FileWhen to read
overview.mdNeed full product overview, infrastructure details, or what’s available across all surfaces
info-api.mdBuilding against the POST /info endpoint - migration, SDK overrides, per-endpoint reference
websocket-api.mdBuilding against wss://hypercore.goldrushdata.com/ws - l2Book aggregated snapshots, l4Book order-level diffs, per-endpoint reference and recipes
streaming.mdBuilding real-time features over the GraphQL Streaming API - wallet firehose, HIP-3 and HIP-4 OHLCV, liquidations and vault events
roadmap.mdWhat’s shipping next - type expansion, time-travel, cross-venue, signed responses