The Hyperliquid Data API is designed to serve builders, quant traders, and protocol analysts who need high-performance access to on-chain and off-chain real-time data. Whether you're building custom execution strategies, monitoring positions, or powering a research dashboard, having direct access to WebSocket and REST endpoints unlocks high-frequency, granular insight into Hyperliquid markets.
For developers seeking canonical reference formats and schemas, the Hyperliquid Data API is fully documented in the official Data API reference. Teams pairing analytics with live order execution also leverage a dedicated Hyperliquid RPC node to ensure end-to-end latency and throughput consistency.
What is Hyperliquid Data API?
The Hyperliquid Data API is the network’s primary read-only interface for accessing market data APIs. It allows clients to query state, stream price feeds, monitor positions, and analyze order flow via two mechanisms:
REST endpoints
WebSocket subscriptions
Where a Hyperliquid RPC node provides write and transaction submission access, the Data API enables non-mutative reads for trades, books, liquidations, and more.
In Hyperliquid’s architecture, which includes HyperCore and HyperEVM, the Data API guarantees consistent access to all relevant state and market updates across analytics and UI clients.
Write operations, such as placing orders or using CoreWriter to initiate on-chain actions, are outside the Data API’s scope and require an RPC connection.
By design, the Data API’s outputs align with on-chain state, which is crucial for accurate Hyperliquid analytics and trustworthy application behavior.Core Features of the Hyperliquid Data API
The Hyperliquid Data API is purpose-built for streaming real-time data feed outputs:
Persistent WebSocket connection to stream:
Live trades
Order book updates with top-of-book and incremental depth
Liquidation feed with event-level detail
Funding updates from the funding rate API
High-availability REST endpoints for:
OHLCV candles
Open interest
L2 snapshots and user portfolios
Deterministic schemas for JSON responses
Subscription-aware sequencing for deduplication and replay
Key Endpoints and Supported Methods
Hyperliquid Data API offers REST HTTP data endpoints access via POST requests to /info, and WebSocket streams via wss://api.hyperliquid.xyz/ws.
REST examples:
Market-level:
allMids, l2Book, candleSnapshot
fundingHistory, openInterest
User-level:
userFills, portfolio, subAccounts, userTwapSliceFills
WebSocket subscriptions:
trades by coin
book for order book updates
liquidations for the liquidation feed
fundingRates for streaming the funding rate API
Understanding REST and WebSocket Access
Builders use REST endpoints for reference data, snapshots, and backfillable history, while persistent WebSocket connections are ideal for streaming live real-time data with low latency.
Design guidelines:
Use ping/pong heartbeats to detect stale WS connections
Handle reconnect logic and resubscription flows
Validate deltas via sequence numbers
Design for burst throughput and backpressure management
Teams building on HyperEVM often use both REST and WebSocket together for redundancy and snapshot validation.
How HypeRPC Enables Access to the Hyperliquid Data API
Imperator’s HypeRPC is a managed access gateway that improves API integration into the Hyperliquid Data API. With HypeRPC, builders don’t need to run their own Hyperliquid nodes or worry about connection nuances. It handles connection orchestration, cross-region routing, and observability.
Capabilities include:
Stable URL routing with global CDN edge presence
Managed WebSocket upgrades with retry support
Logs and metrics for latency, reconnects, and throughput
Support for rate-limiting visualization and saturation tracking
Crucially, using HypeRPC doesn’t require any custom coding for Hyperliquid because it speaks the same API.
Integrating the Hyperliquid Data API into Your Workflow
Typical client architectures follow this pattern:
Use REST endpoints to fetch initial metadata and snapshots
Open a WebSocket connection for live trades and deltas
Stream updates into an in-memory store or message queue
Validate sequencing; trigger backfills on gaps
Archive to time-series DB for analysis or replay
You can also deploy a local order book server that listens to WS streams and persists order book updates at full precision. For low-latency submission and analytics alignment, consider integrating with a reliable Hyperliquid RPC node provider.
Best Practices for Builders and Analysts
To maximize performance, consider these operational patterns:
Optimize for throughput and latency with batch processing and async I/O
Compress deltas and limit retained state where possible
Use circuit breakers for WebSocket disconnects and retries
Monitor dropped messages, lag, and backpressure via metrics
Secure endpoints with TLS (HTTPS/WSS); rotate API wallet keys regularly
Use distinct signers per subaccount to avoid CoreWriter nonce collisions
Building Smarter with the Hyperliquid Data API
The combination of rich data and real-time access opens up powerful use cases on Hyperliquid. For builders, the Hyperliquid Data API enables:
Funding basis models using the funding rate API and trade flows
Execution bots that react to order book updates and queue depths
Liquidation-aware dashboards that overlay real-time data feed insights
Data-science pipelines that build predictive features for signals
Why HypeRPC and Hyperliquid RPC Strengthen Your Data Pipeline
The Hyperliquid Data API delivers depth and control with efficient REST endpoints, event-level WebSocket streams, and stable schemas that power real-time DeFi systems. Pair it with HypeRPC for managed access and a dedicated Hyperliquid RPC node to ship analytics, trading bots, and research pipelines with consistent latency, high uptime, and clear observability.
FAQs
1. What is the Hyperliquid Data API?
The Hyperliquid Data API is a high-throughput market data API that offers REST and WebSocket access to trades, order book updates, funding rate API, and the liquidation feed.
2. How does HypeRPC enable access to the Hyperliquid Data API?
HypeRPC offers globally routed WebSocket connections, logs, retry logic, and performance metrics that enhance API integration and minimize latency.
3. Do I need a Hyperliquid RPC node alongside the Data API?
In most production setups, yes. Use the Data API for reads and market data, and a Hyperliquid RPC node for writes, transaction submission, and state-changing operations
