Every Hyperliquid trade — with the wallet behind it.
Real-time and recent-history data for Hyperliquid core — every trade, L3 order-book update, liquidation, funding payment and open position, each attributed to the address that made it. GraphQL queries, WebSocket subscriptions and Kafka streams.
Live now. API on every plan from $49/mo, streaming from $99/mo · rolling ~30-day history in the API · full archive in the Data Lake.
Representative events — values illustrative.
Hyperliquid's own API aggregates the book to L2 and anonymizes market-wide order flow. Bitquery gives you every order and every fill with the wallet behind it — L3, market-wide, modeled and ready to query. See the comparison →
Why it's different
Data no venue exposes — at any price.
See both sides of every trade.
Every fill carries the trader's address, and every resting order and cancel in the L3 book is attributed to its owner. That's the full order book, order by order, with identity — the basis for market-maker tracking and cancel-to-fill analysis. No centralized exchange exposes this at any price.
PnL and positions, computed by the chain.
Every fill arrives with realized PnL, the fee paid, the leverage in force and the trader's position size before the fill — straight from Hyperliquid's execution engine. Per-wallet PnL, win rates, and profitable-trader leaderboards are a GROUP BY, not a reconstruction project.
Every open position, as a state cube.
CurrentPositions holds every open perp position on the exchange right now — signed size, leverage, margin mode, accumulated funding and realized PnL — filterable by wallet or market. Hourly funding stamps each position again with the rate and the signed amount. Open interest by wallet is a query, not something you rebuild from fills.
What's in the cube
One cube, twelve datasets.
Every dataset is a GraphQL query and a WebSocket subscription on the same schema — change query to subscription and drop limit and orderBy. Subscribe to everything or just what you need.
Trades & order book
what the engine executed · 5 datasetsEvery fill, both sides: price, size, direction, aggressor flag, fees and builder fee, leverage, size before, realized PnL, and the trader, vault and signer.
Docs →The full lifecycle: open, filled, canceled, rejected. Order type, TIF, trigger and reduce-only flags, with the trader on every order.
Docs →Every individual order placed, resized or removed: kind, side, price, size before and after, order id, and the trader's address.
Docs →TWAP orders with state (activated, finished, terminated), executed size and notional, and the trader.
Docs →Perp risk
liquidations, funding, positions, leverage · 4 datasetsExchange-wide liquidations with method (market or backstop), mark price, liquidator and liquidated user, execution and position details.
Docs →Per-trader funding transfers at every hourly tick: signed amount, the rate applied, and position size.
Docs →Every open perp position right now: signed size, leverage, cross or isolated, accumulated funding, realized PnL. Filter by wallet or market.
Docs →Prices & consensus
what went into each block · 3 datasetsLatest mark price per market with the block of last update, including HIP-3 tokenized stocks and indices.
Docs →The feed behind the marks: spot inputs, external-perp prices, daily reference price, update class.
Docs →The lowest level: every signed action submitted to the L1 with its status, accepted or the node's error. User, signer, nonce, vault and bundle hash. Rejected orders live here.
Docs →hyperliquid.candles.proto and hyperliquidcore.messages.proto: fills, order statuses, raw book diffs, TWAP statuses, oracle updates, misc events (funding, ledger, staking), signed actions, and core-writer actions from HyperEVM contracts acting on the core book. Schema on GitHub →What you can build
One cube, three audiences.
Trading apps & retail tools
- Copy-trading feeds (the feed states trade direction directly)
- Whale-alert bots and open-position trackers
- Realized-PnL and win-rate leaderboards
- Real-time liquidation alerts and cascade views
- TWAP "whale is accumulating" watchers
Quant & institutional
- L3 microstructure — with identity on every order
- Cancel-to-fill ratios and order lifetimes per wallet
- Execution quality vs. mark price
- Funding-rate and basis models (external-perp price included)
- Rejected-action signals — measure bot competition invisible in fills
- Backtests on the 30-day API window, or the full archive from the Data Lake
Ecosystem & B2B intelligence
- Builder-code market share — which frontends win order flow, and their revenue
- HIP-3 market and deployer tracking — tokenized stocks and indices by namespace
- Vault performance and flow analytics
- Flow-of-funds: deposits, withdrawals, spot↔perp transfers
- Staking, validator, and chain-health dashboards
- Cross-chain: follow a wallet before and after its Hyperliquid positions
How it works
GraphQL, WebSocket, Kafka — or the archive over S3.
Query it, subscribe to it, or take the raw feed. Every dataset shares one schema, so an order's placement, its life in the book, and its fills all line up by wallet and block. The protobuf schema is open source — decode it yourself, no vendor lock-in.
bitquery/streaming_protobuf · hyperliquid/ →
subscription { Hyperliquid { Trades { Block { Number Time } Trade { Market { Symbol Kind IsPerp } Execution { Price Size Side Direction IsAggressor Oid Tid } Fees { Fee FeeToken } IsTwap Position { Leverage IsCross Side RealizedPnl } Trader { Address } } } } }
Availability
Live now, with history.
Real-time
Every dataset as a WebSocket subscription on the streaming API, or as Kafka streams for the lowest latency.
Recent history
A rolling ~30-day window on every dataset for GraphQL queries: leaderboards, cancel-to-fill ratios, funding paid per wallet.
Full archive
The Blockchain Data Lake serves the complete Hyperliquid history — trades, orders, book updates, liquidations, funding, TWAPs, signed actions and candles — over S3.
Modeled correctly
So you don't have to.
Hyperliquid's raw feed has sharp edges. We've modeled all of it, and published the schema so you can verify every field.
- The two sides of a trade are paired on the right key.
- TWAP fills — which carry no transaction hash — are handled.
- Prices keep full decimal precision.
- Rejected actions are in
SignedActionswith the node's error status — never silently dropped.
FAQ
Questions, answered precisely.
HyperCore vs. HyperEVM — which is this?
Is historical data available?
How is this different from Hyperliquid's own API?
What markets are covered?
How is the data delivered?
What does it cost?
Do I need an API key?
Can I decode it myself?
Start streaming Hyperliquid data.
Streams on Pro and Scale. Sign up, generate a token, and run the Trades subscription from the docs in the IDE — the same query works as a WebSocket stream in your own stack.