Crypto Order Book L3 Data

Crypto Order Book L3 Data

CoinAPI provides normalized Level 3 (Market-by-Order) cryptocurrency order book data where supported by the source exchange and symbol.

When available, Level 3 exposes individual passive orders, including order identifiers, price, size, timestamps, and order-level updates. Availability depends on the exchange, market, and delivery method.

What Is Crypto Order Book L3 Data?

Level 3 order book data shows the individual orders inside the order book.

Unlike Level 2 order book data, which aggregates liquidity by price level, Level 3 (Market-by-Order) preserves individual passive orders when the exchange provides them. Each bid and ask represents a specific order with its own identifier, price, and size — useful when developers need to study how liquidity changes inside the queue, not only how much total volume exists at each price.

L3 availability depends on the exchange and market. If the data source only provides Level 2 depth, CoinAPI may fall back to Level 2 format. In that case, order IDs can be null or not provided, and entries without IDs should be treated as aggregated Level 2 entries.

Confirmed L3 coverage is venue- and market-specific. CoinAPI includes examples such as Coinbase, Bitso, and Bitstamp markets where L3-capable symbols are available.

Level 3 data is most useful when the application needs to follow the full lifecycle of resting orders, including when liquidity is added, updated, reduced, or removed from the book. This allows developers to study queue behavior, order placement patterns, cancellations, and short-term liquidity shifts at a much more granular level than aggregated market depth.

Because every visible order can be tracked separately when supported by the exchange, L3 data is often used for market microstructure research, advanced market making, queue-position modeling, latency analysis, and order-flow prediction. It can also help identify behavior that is hidden in Level 2 data, such as repeated order cancellations, layering patterns, or liquidity appearing and disappearing around key price levels.

What's Included in CoinAPI Order Book L3 Data?

CoinAPI L3 order book data contains bid and ask entries with order-level information when available.

FieldWhat it means
symbol_idCoinAPI normalized symbol identifier
time_exchangeTimestamp reported by the exchange
time_coinapiTimestamp when CoinAPI received the order book
asksAsk-side order entries, ordered from best to worst price
bidsBid-side order entries, ordered from best to worst price
idOrder identifier when provided by the source
pricePrice of the bid or ask order
sizeBase asset amount resting on the order
update_typeWebSocket update action for an order-level change

WebSocket L3 messages additionally include:

  • sequence
  • is_snapshot

The update_type field describes how an order changes after the initial snapshot. Supported values include ADD, UPDATE, SUBTRACT, DELETE, and MATCH.

Together, these fields provide the information needed to track order-level changes, monitor passive liquidity, analyze queue behavior, and study how the order book changes before and after trades.

Available REST Endpoints

CoinAPI provides REST endpoints for retrieving current L3 order books across symbols or for a specific symbol. REST is suited for requesting current L3 snapshots. For continuously updated order-by-order changes, use the CoinAPI WebSocket API.

Current L3 Order Books

Returns current L3 order books across symbols, with optional symbol filtering.

Response includes
  • CoinAPI symbol identifier
  • exchange and CoinAPI timestamps
  • ask-side entries
  • bid-side entries

filter_symbol_id supports comma- or semicolon-delimited symbol identifier parts. limit_levels controls the maximum number of levels included in the response. API key authentication is required, and L3 availability depends on source venue and market support.

Current L3 Order Book by Symbol

Returns the current L3 order book for a specific CoinAPI symbol. L3 order books include individual order IDs for each price level when provided by the data source.

Response includes
  • CoinAPI symbol identifier
  • exchange and CoinAPI timestamps
  • ask-side orders
  • bid-side orders
  • order identifiers when available
  • price and size for each entry

symbol_id must be a valid CoinAPI symbol from Metadata → Symbols, and limit_levels controls the maximum number of levels returned. If the source only provides Level 2 depth, order IDs may be null or not provided — entries without order IDs should be treated as Level 2 aggregated entries. API key authentication is required.

Live Order Book L3 Streaming with WebSocket

For applications requiring order-by-order market depth, CoinAPI provides Level 3 order book streaming through the WebSocket API. A book_l3 message is sent for each snapshot or update of the order book in Level 3 format.

After subscribing to this data type, CoinAPI starts delivering order book updates immediately, and at least one snapshot is provided as soon as possible with the nearest book update.

Unlike Level 2, Level 3 does not aggregate liquidity by price level when order-level data is available. Each ask and bid corresponds to a passive order with its own price, size, and order identifier. Snapshot messages represent the initial collection of orders in the book, and later messages modify that collection using update_type.

Supported update types include:

Update typeWhat it means
ADDAdd an order to the price queue
UPDATEUpdate the order size in the price queue
SUBTRACTSubtract size from the order in the price queue
DELETEDelete the order from the price queue
MATCHSubtract order size because of a match

If the data source only provides Level 2 order book resolution, the L3 stream can fall back to Level 2. In that case, order IDs can be null or missing, and the entry should be treated as aggregated Level 2 data.

CoinAPI Order Book L3 Dataset Characteristics

  • Available through REST API and WebSocket API
  • Current Level 3 order books available through REST
  • Order-level market data where supported by the exchange
  • Individual order identifiers included when provided by the data source
  • WebSocket delivers snapshots followed by incremental order-level updates
  • Snapshot messages represent the current state of the order book
  • Incremental messages modify existing orders using ADD, UPDATE, SUBTRACT, DELETE, and MATCH
  • ISO 8601 UTC timestamps
  • Normalized CoinAPI symbol identifiers
  • Configurable retrieval depth using limit_levels
  • If the source exchange does not provide Level 3 order data, order identifiers may be unavailable or omitted
  • L3 availability is venue- and market-specific

Why Developers Use Order Book L3 Instead of Order Book L2

Both datasets describe market liquidity, but they answer different questions.

Level 2 aggregates liquidity by price level, making it suitable for monitoring market depth and estimating execution costs. Level 3 preserves individual passive orders whenever the exchange provides them, allowing developers to analyze queue dynamics and order-level behavior.

If you need…Use
Aggregated liquidity by price levelOrder Book L2
Best available market depthOrder Book L2
Individual passive ordersOrder Book L3
Queue position analysisOrder Book L3
Order lifecycle analysisOrder Book L3
Market microstructure researchOrder Book L3
Order-level execution modelingOrder Book L3

Many quantitative trading systems combine both datasets. Level 2 provides a compact view of available liquidity, while Level 3 adds the order-level detail needed to study queue behavior and execution dynamics.

Common Crypto Order Book L3 Use Cases

  • Analyze queue position
  • Build execution algorithms
  • Research market microstructure
  • Monitor order lifecycle events
  • Power AI trading applications
  • Study liquidity dynamics

Who Uses Crypto Order Book L3 Data?

  • Quantitative trading firms
  • Algorithmic trading systems
  • Market making firms
  • Academic researchers
  • AI and machine learning teams
  • Exchange analytics platforms
Crypto Order Book L3 Data

Ready to Build with CoinAPI Order Book L3 Data?

Explore the Order Book L3 documentation to retrieve current Level 3 order books through REST and stream real-time order-by-order updates with the CoinAPI WebSocket API.

When available from the underlying exchange, Level 3 data provides individual order identifiers and lifecycle events that extend beyond aggregated Level 2 market depth.