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 Overview
Quick Reference
| Item | Value |
|---|---|
| Info API URL | https://hypercore.goldrushdata.com/info |
| Method | POST |
| Authentication | Authorization: Bearer <GOLDRUSH_API_KEY> (same key as Foundational/Streaming/Pipeline) |
| Rate Limit | None |
| Wire compatibility | Byte-for-byte with POST api.hyperliquid.xyz/info for implemented types |
| Networks | Mainnet only |
| HyperCore historical depth | Block 676,607,001 onward (2025-07-27T01:49:59Z) |
| HyperEVM historical depth | Genesis |
Surfaces
| Surface | What it provides |
|---|---|
| Info API | Drop-in replacement for POST /info (6 native types; unsupported types return a JSON error) |
| Streaming API | Real-time walletTxs, ohlcvCandlesForPair, ohlcvCandlesForToken |
| Pipeline API | hl_fills, hl_trades, hl_orders, hl_funding, hl_misc_events to your warehouse |
| Foundational API | HyperEVM (chain 999) token balances, transfers, NFTs, gas |
GoldRush is the complete data layer for Hyperliquid. It aggregates everything you need to build on Hyperliquid - HyperCore, HIP-3, HIP-4, and HyperEVM - under one API key.
Drop-in Info API
Same/info request body. Change one URL and one header to remove rate limits and unlock more data. Hosted at hypercore.goldrushdata.com.
Real-time Streaming
Wallet firehose, OHLCV for every HIP-3 and HIP-4 market the moment it goes live, and pre-decoded liquidations and vault events.Pipeline to your warehouse
Landhl_fills, hl_trades, hl_orders, hl_funding, and more directly in ClickHouse, BigQuery, Postgres, Kafka, or S3.
HyperEVM coverage
Token balances, transfers, approvals, NFTs, and gas for HyperEVM - same shape as every other EVM chain on GoldRush.Why GoldRush for Hyperliquid
The public Hyperliquid/info API is generous, but it has hard limits that most production apps run into:
- 1200 weight/min/IP rate limits per address.
- 1000 WebSocket subscriptions per IP - not enough to track every active trader.
userFillscapped at ~10,000 rows - active traders blow through that in weeks.- Liquidations buried inside fills as a thin stub; vault, staking, and delegation data arrives untyped.
- HIP-3 and HIP-4 discovery is manual -
candleSnapshotis poll-based and effectively limited to mainstream markets. - No HyperEVM concept at all - DEXes, NFT mints, and lending live on chain
999and the/infoAPI doesn’t see them.
What’s included
| Surface | What you get | Where to start |
|---|---|---|
| Info API | Drop-in replacement for POST /info. Same request body, no rate limits, faster orderbook reads, batched user state, builder-attribution data. | Info API Overview |
| Streaming API | Real-time walletTxs, ohlcvCandlesForPair, ohlcvCandlesForToken over GraphQL/WebSocket. Pre-decoded HyperCore events. | Wallet firehose, HIP-3 markets |
| Pipeline API | Push hl_fills, hl_trades, hl_orders, hl_funding, hl_misc_events into your warehouse continuously. | HyperCore normalizers, Stream Hyperliquid trades to ClickHouse |
| Foundational API | HyperEVM token balances, transfers, approvals, NFTs, gas, blocks. | HyperEVM chain page |
| Live analytics | HIP-3 Market Screener, Liquidation Cascade Map, Market Health Score at hyperliquid.goldrush.dev. | Live tools |
Infrastructure
- Dedicated Hyperliquid nodes in Tokyo - colocated with Hyperliquid’s validator infrastructure for low-latency reads.
- Private backbone for high-throughput data ingestion.
- No rate limits - bypass the public
/infoand WebSocket constraints entirely. - Full historical backfill - every fill, funding payment, and ledger event back to HyperCore block
676,607,001(2025-07-27T01:49:59Z). HyperEVM coverage goes back to genesis.
Quickstart
Three “first 5 minutes” paths - pick whichever maps to what you’re building.Replace one URL
Already usingapi.hyperliquid.xyz/info? Change the URL and add one header.
Open a wallet stream
Subscribe to thousands of HyperCore wallets in one connection.Land fills in your warehouse
Streamhl_fills into ClickHouse, BigQuery, or Postgres.
Pick the path that matches what you’re building. All three use the same GoldRush API key.
Prerequisites
A GoldRush API key. Sign up at goldrush.dev/platform.Vibe Coders
$10/mo - Built for solo builders and AI-native workflows.Teams
$250/mo - Production-grade with priority support.1. Drop-in Info API
If your code already callsPOST https://api.hyperliquid.xyz/info, swap the URL to https://hypercore.goldrushdata.com/info and add an Authorization: Bearer header. The request body and response shape stay byte-for-byte identical.
cURL
TypeScript
Python
Info API Migration Guide
Side-by-side examples in JS, Python, and cURL - including how to point existing SDKs at GoldRush.2. Stream wallet activity
Subscribe to one or many HyperCore wallets in real time over WebSocket. Pre-decoded events include fills with liquidation context, funding payments, vault actions, and 20+ ledger subtypes.GoldRush SDK
Install
walletTxs subscription has zero rate limits and scales to thousands of concurrent wallet subscriptions per connection. See Wallet firehose for the full pattern.
3. Pipe fills to your warehouse
Stream HyperCore fills into ClickHouse, BigQuery, Postgres, Kafka, or S3 with one config - no ETL on your side. Create a pipeline In the GoldRush Platform, navigate to Manage Pipelines and click Create Pipeline. Pick HyperCore + Fills Choose Hyperliquid as the chain and Fills as the data type. Choose your destination Connect ClickHouse, BigQuery, Postgres, Kafka, S3/GCS/R2, SQS, or a Webhook. Deploy Fills begin flowing within seconds. Full walkthrough with sample SQL: Stream Hyperliquid trades to ClickHouse.4. Fan out across many wallets
Need account state for many wallets at once?batchClearinghouseState and batchSpotClearinghouseState accept 1 to 50 wallets per call and fan them out in parallel against our private node. There is no equivalent on the public Hyperliquid /info API.
Each slot in the response is either the raw upstream object for that wallet (success) or a thin error envelope ({error, user, message}) when an individual wallet fails. The HTTP status stays 200 OK even on partial failure - always check for the error key on each slot.
TypeScript
cURL
users are removed (case-insensitive); input order is preserved for the survivors.
For batches larger than 50, issue multiple calls. Use cases: portfolio dashboards, multi-wallet PnL aggregators, fleet-level liquidation risk monitoring, treasury balance reconciliation. Full reference: batchClearinghouseState, batchSpotClearinghouseState.
What’s next
HIP-3 markets
Real-time OHLCV for every builder-deployed perp market - equities, commodities, niche assets.Liquidations & vault events
Pre-decodedLedgerLiquidation, LedgerVaultDeposit, LedgerVaultWithdraw, and 17 more subtypes.