Order Book L4: The Complete Guide to Level 4 Order Book Data

Most order books tell you how much liquidity exists at a price.

Order Book L4 tells you which individual orders created that liquidity, who placed them, and what happens to those orders next.

That difference matters.

An aggregated book might show 20 BTC available at a given price. Level 4 data can expose the individual orders behind those 20 BTC and follow them as they are placed, modified, partially executed, canceled, or filled.

For quantitative researchers, market makers, execution teams, and developers studying market microstructure, that creates a much more detailed view of how liquidity actually behaves.

CoinAPI provides this level of visibility for Hyperliquid through its dedicated Level 4 data infrastructure, with both real-time WebSocket DS streaming and historical Flat Files.

What Is Order Book L4?

Order Book L4, or Level 4 order book data, is an unaggregated market data feed that exposes individual orders together with their observable lifecycle and exchange-specific metadata.

Instead of representing the book only as liquidity grouped by price, each resting order can be treated as a separate object.

For Hyperliquid, CoinAPI's book_l4 feed includes fields such as:

Identifiers for related child orders

This means an application can follow much more than price and size.

It can study the actual evolution of orders inside the market.

L1 vs L2 vs L3 vs L4 Order Book Data

The easiest way to understand L4 is to compare it with the other common market data levels.

L1 answers:

What is the current best price?

L2 answers:

How much liquidity is available at each price?

L3 answers:

Which individual orders make up that liquidity?

L4 can go further:

What is happening to those orders over time?

That distinction becomes especially useful when studying a market where orders are continuously created, amended, reduced, matched, and removed.

How an L4 Order Book Works

Consider a simplified L2 order book:

At $110,000, all you know is that the visible aggregated size is 14.2 BTC.

An L4 feed can reveal that this liquidity consists of multiple separate orders.

Those orders may have different identifiers, sizes, users, order types, and lifecycle states.

More importantly, you can observe what happens next.

CoinAPI's Hyperliquid book_l4 incremental stream supports lifecycle updates including:

• ADD — an order is accepted into the book
• UPDATE — an existing order changes
• SUBTRACT — its size is reduced
• DELETE — the order is removed
• MATCH — its size is reduced due to execution

The order book is therefore no longer just a sequence of snapshots.

It becomes a stream of individual state changes.

Why Individual Order Lifecycles Matter

A price level can remain almost unchanged while the orders behind it change dramatically.

Imagine that an L2 feed continues to show roughly $2 million of bid liquidity near the market.

Underneath that number, participants might be continuously canceling and replacing orders. New liquidity may be entering the queue while older orders disappear. Some orders may remain stable while others survive for only a short period.

Those behaviors are difficult to study from aggregated depth alone.

With Level 4 order book data, researchers can investigate:

Order persistence. How long does liquidity remain available?

Cancellation behavior. How frequently are orders removed before execution?

Liquidity replenishment. Does new liquidity appear after existing orders are matched or canceled?

Order arrival rates. How quickly are new orders entering the market?

Queue dynamics. How does the composition of liquidity change over time?

Participant behavior. Do particular observable wallets repeatedly provide, remove, or consume liquidity?

The result is a different type of market dataset.

Instead of only studying prices, you can study the process that creates them.

L4 Order Book Data on Hyperliquid

Hyperliquid is particularly interesting for Level 4 analysis because its observable data can include information rarely available in conventional aggregated crypto feeds.

CoinAPI's Hyperliquid L4 infrastructure exposes six complementary feed families:

Normalized raw system action events

These feeds can be consumed through a single dedicated WebSocket DS connection.

This matters because an order book does not exist in isolation.

Researchers can correlate changes in individual orders with executions, oracle movements, TWAP activity, and exchange-native events.

Wallet Attribution Changes What You Can Analyze

One of the most distinctive characteristics of Hyperliquid L4 data is participant attribution through observable wallet or account information.

The book_l4 feed can associate passive orders with the relevant user, while trade_l4 includes maker and taker wallet attribution.

This enables research that cannot be performed with anonymous aggregated L2 depth alone.

For example, analysts can study whether an observable participant tends to provide or consume liquidity, how long its orders typically remain in the book, how its activity changes during volatile periods, and how its executions relate to its previous resting orders.

This makes Level 4 useful not only for reconstructing the book, but also for wallet behavior and participant-level market microstructure research.

Order Book L4 vs Trade Data

Trade data and L4 data answer different questions.

A trade tells you that two orders interacted and an execution occurred.

But executions are only part of order book activity.

Orders can be placed and canceled without trading. Their size can change. They can be removed. New liquidity can replace old liquidity at the same price.

If you only analyze trades, much of this activity remains invisible.

L4 allows researchers to study both executed and non-executed order activity.

That is important when researching liquidity because the decision to cancel an order can sometimes be just as informative as the decision to place one.

Reconstructing an Order Book From L4 Data

CoinAPI's book_l4 stream provides an initial snapshot followed by incremental updates.

A consumer can therefore maintain its own representation of the book.

The basic workflow is:

1. Subscribe to book_l4.
2. Receive the initial order book snapshot.
3. Store individual orders by their identifiers.
4. Apply incoming ADD, UPDATE, SUBTRACT, DELETE, and MATCH events.
5. Continuously update the local order book state.

Instead of repeatedly downloading complete snapshots, the system maintains the book by applying only the changes.

This model is useful for market replay, queue analysis, execution simulation, and other research where the sequence of events matters.

More Than an Order Book: Combining the Six L4 Feeds

The real analytical value becomes clearer when book_l4 is combined with the other Hyperliquid feeds.

Order Book + Trades

Combine book_l4 with trade_l4 to connect changes in resting liquidity with actual executions.

This can support order flow analysis, execution-quality research, and participant behavior studies.

Order Book + Oracle Prices

Combine book_l4 with hl_oracle_prices to compare visible liquidity with changes in oracle and mark prices.

This can support research into price divergence, risk conditions, and market behavior around rapid price movements.

Order Book + TWAP Activity

hl_twap_statuses exposes TWAP lifecycle and execution progress.

Researchers can study how scheduled execution interacts with liquidity and market conditions over time.

Order Book + Raw Exchange Events

hl_misc_events and hl_system_events expose normalized event envelopes containing exchange-level information such as block numbers, event types, and JSON payloads.

These streams are useful for observability, auditing, and more specialized exchange-native research.

Real-Time Order Book L4 Data

For live applications, CoinAPI provides a dedicated Hyperliquid WebSocket DS endpoint:

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

Applications can subscribe to one or several L4 feed families within the same session.

Symbol-scoped streams include:

book_l4
trade_l4
hl_oracle_prices
hl_twap_statuses

Exchange-scoped streams include:

hl_misc_events
hl_system_events

CoinAPI delivers observable order mutations without waiting for block confirmations before streaming the order book updates.

For latency-sensitive applications, this provides visibility into changes as the market evolves rather than reducing the feed to block-level batches.

Historical Order Book L4 Data

Real-time L4 is useful for production systems.

Historical L4 is what makes the same level of detail useful for research.

CoinAPI also provides historical Hyperliquid L4 datasets through Flat Files delivered using AWS S3 infrastructure.

Files are compressed as CSV.gz and refreshed hourly.

Historical and real-time delivery use aligned field naming conventions and CoinAPI symbol identifiers. That allows teams to reuse schema definitions and validation logic across research and production workflows while accounting for the different delivery formats.

Historical L4 data can be used for:

• market replay
• historical order book reconstruction
• cancellation analysis
• queue research
• execution simulations
• liquidity studies
• market microstructure research
• machine learning datasets
• strategy backtesting

Instead of collecting a WebSocket stream for months before research can begin, teams can work with existing historical files.

When Do You Actually Need L4?

Not every application needs Level 4 data.

If you are displaying a simple ticker, L1 may be enough.

If you need a depth chart or aggregated liquidity analysis, L2 may be enough.

If you need individual passive orders across supported exchanges, L3 may be appropriate.

L4 becomes relevant when the behavior and lifecycle of individual orders are part of the question you are trying to answer.

That includes applications involving:

• detailed order flow research
• order lifecycle monitoring
• queue dynamics
• cancellation behavior
• participant or wallet analysis
• liquidity forecasting
• execution-quality research
• historical market replay
• advanced market-making research
• market microstructure modeling

In other words, you need L4 when knowing the amount of liquidity is no longer enough.

You need to understand how that liquidity was created, changed, executed, and removed.

Access Order Book L4 Data With CoinAPI

CoinAPI provides Hyperliquid Level 4 order book data for both real-time and historical workflows.

Stream book_l4, trade_l4, oracle prices, TWAP statuses, and raw Hyperliquid event feeds through the dedicated WebSocket DS infrastructure. For historical research, access L4 datasets through compressed Flat Files delivered using AWS S3 infrastructure.

Use the same data source from historical research and market replay through to live production systems.

Explore the Hyperliquid L4 documentation or get your API key and start with free credits.

Related Topics

• What Is Level 4 (L4) Order Book Data?
• CoinAPI Introduces Hyperliquid L4 Data
• Tracking the Whales: Using Hyperliquid L4 Wallet Data for an Edge
• Building a Reproducible Hyperliquid Order Book Replay from CoinAPI Book L4 Flat Files
• What Data Is Available Through CoinAPI WebSocket DS for Hyperliquid?
• Demystifying Level 4 (L4) Order Book Data: Why Waiting for Block Confirmations Is Dead on Arrival