Hyperliquid L4 Data API

Hyperliquid L4 Data

Access raw Hyperliquid Level 4 data through CoinAPI's dedicated WebSocket DS infrastructure. Stream individual order lifecycle events, executed trades with wallet attribution, oracle prices, TWAP execution status, and raw node events from a single connection.

Historical datasets are also available through CoinAPI Flat Files using aligned schemas for research and production workflows.

Explore the Docs Get Your API Key

What Is Hyperliquid Level 4 Data?

Most market data feeds aggregate liquidity before distributing it to users. Even traditional Level 2 and Level 3 feeds simplify what actually happens inside the matching engine.

Level 4 (L4) data exposes the raw order lifecycle. Instead of showing aggregated liquidity or individual resting orders alone, L4 follows every order as it moves through the exchange. Developers can observe order placement, modification, partial execution, cancellation, rejection, and complete fills as they occur.

For Hyperliquid, CoinAPI delivers this information directly through a dedicated WebSocket DS feed without waiting for block confirmations. In addition to order book mutations, the feed includes executed trades, oracle prices, TWAP execution updates, and raw node events.

This dataset is designed for applications that require the highest available level of market transparency.

What's Included?

The Hyperliquid L4 feed consists of six complementary data streams delivered through a single WebSocket DS endpoint.

Feed	What it provides
book_l4	Order-by-order Level 4 order book snapshots and incremental updates
trade_l4	Executed transactions with taker and maker wallet attribution
hl_oracle_prices	Oracle prices, mark prices, daily values, and price inputs
hl_twap_statuses	TWAP execution progress, lifecycle, and completion status
hl_misc_events	Raw Hyperliquid node events with normalized envelopes
hl_system_events	Raw system action events with normalized payloads

The book_l4 Feed's Detailed Order Metadata

The book_l4 feed additionally includes detailed order metadata such as:

Field	What it means
id	Exchange-provided order identifier
price	Order price
size	Current order size
user	Hyperliquid wallet or account associated with the order
cloid	Client order identifier when provided
order_type	Exchange order type
orig_size	Original order size
update_type	Lifecycle action applied to the order

Field	What it means
hl4_status	Hyperliquid order status
tif	Time-in-force value
reduce_only	Indicates whether the order is reduce-only
trigger_px	Trigger price for stop or take-profit orders
trigger_condition	Human-readable trigger condition
children	Nested child orders attached to a parent order
children_oids	Child order identifiers for bracket orders

Together, these feeds expose the full observable lifecycle of Hyperliquid orders together with execution, oracle, TWAP, and exchange-native events.

Available Delivery Methods

Hyperliquid L4 data is available through CoinAPI's dedicated WebSocket DS infrastructure for real-time streaming and through Flat Files for historical analysis.

WebSocket DS

Real-time Hyperliquid L4 data is delivered through a dedicated endpoint:

wss://hyperliquidl4.ws-ds.md.coinapi.io/

After connecting, clients subscribe to one or more feed families using a standard hello message.

Developers can subscribe to:

book_l4
trade_l4
hl_oracle_prices
hl_twap_statuses
hl_misc_events
hl_system_events

Use the CoinAPI Metadata REST endpoints to discover available HYPERLIQUIDL4_* symbols before subscribing.

Flat Files

Historical Hyperliquid L4 datasets are available as hourly refreshed CSV.gz Flat Files hosted on AWS S3.

Flat Files use aligned field naming conventions with the WebSocket DS feed, allowing research and production systems to share the same schema definitions without separate ingestion logic.

Bulk historical access without replaying WebSocket streams.
Compressed CSV.gz files for efficient storage and processing.
AWS S3 delivery for automated and parallel downloads.
Consistent schema with WebSocket DS for shared ingestion logic.
Useful for backtesting, market replay, and order book research.

Live Hyperliquid L4 Streaming

Unlike traditional market data feeds, Hyperliquid L4 streams every observable order mutation instead of waiting for block confirmations or publishing aggregated snapshots.

For book_l4, snapshot messages contain the current visible order book. Incremental updates include only the orders that changed.

Supported order lifecycle updates include:

Update Type	Description
ADD	Order accepted into the order book
UPDATE	Existing order modified
SUBTRACT	Order size reduced
DELETE	Order removed
MATCH	Order size reduced because of an execution

Executed trades are delivered separately through the trade_l4 feed and include both maker and taker wallet attribution. Oracle feeds provide continuously updated mark and oracle prices, while TWAP feeds report execution progress and lifecycle state for TWAP orders.

Raw node event feeds expose normalized Hyperliquid system and miscellaneous events for observability, auditing, and infrastructure monitoring.

Hyperliquid L4 Dataset Characteristics

Available through the dedicated Hyperliquid WebSocket DS endpoint
Historical datasets available through CoinAPI Flat Files
Supports six real-time feed families from a single WebSocket connection
Streams raw Level 4 order lifecycle events without aggregating liquidity
Order book updates include exchange order identifiers when provided
Tracks complete order lifecycles including placement, modification, partial execution, cancellation, rejection, and fills
Includes wallet attribution for passive orders and executed trades
Supports advanced order metadata including Time-In-Force, Reduce-Only, trigger prices, trigger conditions, and bracket order relationships
Symbol-level feeds available for order books, trades, oracle prices, and TWAP statuses
Exchange-level feeds available for raw node events and system events
ISO 8601 UTC timestamps
CoinAPI normalized Hyperliquid symbol identifiers

Why Developers Use Level 4 Instead of Level 3

Level 3 (Market-by-Order) exposes individual passive orders when the exchange provides them. Level 4 goes one step further by exposing the complete observable order lifecycle together with exchange-specific metadata and additional market infrastructure feeds.

For Hyperliquid, Level 4 extends beyond the order book itself by including wallet attribution, oracle updates, TWAP execution status, and raw node events through the same streaming infrastructure.

If you need…	Use
Individual passive orders	Order Book L3
Order identifiers	Order Book L3
Complete order lifecycle	Hyperliquid L4
Wallet attribution	Hyperliquid L4
Oracle and mark prices	Hyperliquid L4
TWAP execution monitoring	Hyperliquid L4
Raw node events	Hyperliquid L4
Exchange-native execution research	Hyperliquid L4

Many quantitative research systems combine both datasets. Level 3 provides a normalized Market-by-Order view across supported exchanges, while Hyperliquid L4 delivers exchange-native order lifecycle data for applications that require the highest available level of market detail.

Common Hyperliquid L4 Use Cases

Build low-latency execution systems
Monitor complete order lifecycles
Track wallet-level trading activity
Analyze TWAP execution
Monitor oracle and mark prices
Build exchange observability pipelines
Research market microstructure

Who Uses Hyperliquid L4 Data?

High-frequency trading firms
Quantitative researchers
Market making firms
Execution analytics platforms
AI trading systems
Exchange infrastructure teams

Hyperliquid L4 Data

Ready to Build with Hyperliquid L4?

Explore the Hyperliquid L4 documentation to stream raw Level 4 order book mutations, executed trades with wallet attribution, oracle updates, TWAP execution status, and normalized node events through CoinAPI's dedicated WebSocket DS infrastructure.

Whether you're building execution algorithms, monitoring market structure, or researching order lifecycle behavior, Hyperliquid L4 provides exchange-native market data with aligned historical Flat Files for seamless transition from research to production.