Incremental Order Book Update

An incremental order book update is a market data message that changes only the affected price levels or orders in an order book rather than sending the full book state.

back to all terms

An order book represents current buy and sell liquidity for a trading pair or instrument. A full snapshot contains the complete visible state of the book at a point in time, while an incremental order book update contains only the changes needed to move from one state to the next.

For example, an incremental update may say that the bid size at a specific price increased, an ask level was removed, or a new order appeared at a price level. Consumers apply these updates in sequence to a known starting state, usually a seed snapshot, to maintain a local copy of the order book.

Incremental updates depend on ordering and continuity. If updates are processed out of order, skipped, duplicated, or applied to the wrong starting snapshot, the reconstructed book can become inaccurate. This is why sequence numbers, sequence gap detection, reset handling, and replay rules are important for order book data.

Incremental order book updates matter because they allow high-frequency market data systems to track book changes efficiently. Sending a complete order book after every change would be expensive, slow, and impractical for liquid markets with many updates per second.

They also support accurate replay, backtesting, liquidity analysis, and trading infrastructure when they are paired with reliable snapshots and sequence metadata. Without correct incremental processing, a system may display stale liquidity, miss changes in market depth, or make trading decisions from an invalid local book.

A snapshot shows the full order book state at one moment. An incremental order book update shows only the changes since a previous state. A snapshot can initialize or reset the book, while incremental updates keep the book current between snapshots.

If an incremental update is missed, the local order book may no longer match the exchange or data provider state. The usual response is to detect the sequence gap, stop trusting the local book, and rebuild from a fresh seed snapshot or replayable full-depth data.

Incremental updates are state transitions. Applying them in the wrong order can create an invalid book because each update assumes that all previous updates have already been processed. Sequence numbers or canonical replay rules help enforce the correct order.

Suppose a BTC/USD order book has a bid level at 50,000 with size 2.5 BTC. An incremental update arrives indicating that the size at 50,000 is now 1.7 BTC. Instead of sending the whole order book, the feed sends only that changed level. The consumer applies the update to its local book and continues processing the next sequenced update.

If the next expected update number is 105 but the consumer receives 107, updates may be missing. The consumer should treat the book as potentially invalid until it can recover using a snapshot or replay process.

CoinAPI Market Data API provides normalized access to exchange market data, including order book and quote-related data that can be used for analytics, trading systems, historical research, and replay workflows. Understanding incremental order book updates helps users interpret how book state changes over time and why snapshot, sequencing, and replay logic are important when reconstructing market depth.

Crypto API made simple: Try now or speak to our sales team

Start for FreeGet in Touch