This is an old revision of the document!
Quote Feed
The Quote Feed provides real-time market data in two formats: Market by Price (MBP) and Market by Order (MBO).
- Market by Price (MBP) – Aggregates orders at each price level, showing the best bid/offer (BBO) or a depth of market (DOM) view, typically up to 10 levels.
- Market by Order (MBO) – Provides a full order book, showing each individual order at its exact price level.
The available depth and data type depend on the subscription request and the user’s market data setup.
Market by Price (MBP)
MBP provides an aggregated view of the market. It groups orders at each price level, showing either:
- Top of Book (BBO) – The best bid and offer.
- Depth of Market (DOM) – Typically the 10 best bid/offer levels.
MBP Data Structure
MBP data is structured in MarketDepthBuffer and MarketDepthLevel messages.
Field | Description |
---|---|
MarketId | The identifier for the market. |
Levels | A list of price levels. Each level represents an aggregate of orders. |
MarketDepthLevel fields:
Field | Description |
---|---|
Price | The price level for the bids/offers. |
BidVolume | The total volume available at this bid price. |
AskVolume | The total volume available at this ask price. |
MBP Subscription Example
To receive MBP data, clients send a MarketDepthSubscribe message.
MarketDepthSubscribe { MarketId = "XCME_C ES (M25)", SubscriptionType = MarketDepthSubscriptionType.Normal, DepthLevels = 10 }
Unsubscribing
To stop receiving MBP data, clients send a MarketDepthUnsubscribe message.
MarketDepthUnsubscribe { MarketId = "XCME_C ES (M25)" }
MBP Message Handling
After subscribing, the following messages are received:
- MarketDefinition – Sent once per market, unless already received via another feed.
- MarketSnapshot – Provides a full market state on initial subscription.
- MarketDepthUpdate – Sends incremental changes to depth.
Example MBP message handling:
private void HandleMarketMessage(ServerMessage serverMessage) { switch (serverMessage.PayloadCase) { case ServerMessage.PayloadOneofCase.MarketDefinition: ProcessMarketDefinition(serverMessage.MarketDefinition); _logger.LogInformation("Received market definition: {MarketId}", serverMessage.MarketDefinition.MarketId); break; case ServerMessage.PayloadOneofCase.MarketSnapshot: ProcessMarketSnapshot(serverMessage.MarketSnapshot); _logger.LogInformation("Received market snapshot: {MarketId}", serverMessage.MarketSnapshot.MarketId); break; case ServerMessage.PayloadOneofCase.MarketDepthUpdate: ProcessMarketDepthUpdate(serverMessage.MarketDepthUpdate); _logger.LogInformation("Received depth update for market: {MarketId}", serverMessage.MarketDepthUpdate.MarketId); break; default: _logger.LogWarning("Unhandled Market Message: {PayloadCase}", serverMessage.PayloadCase); break; } }
Market by Order (MBO)
MBO provides a detailed view of the market by reporting every individual order in the book. Unlike MBP, which aggregates orders at price levels, MBO allows clients to track order-level movements.
MBO data includes:
- Full Order Book Snapshot – Sent when first subscribing.
- Incremental Updates – Sent in real-time as new orders enter or exit the book.
MBO Subscription Example
Example MarketDepthSubscribe message for MBO:
MarketDepthSubscribe { MarketId = "XCME_C ES (M25)", SubscriptionType = MarketDepthSubscriptionType.ByOrder }
Unsubscribing
Example MarketDepthUnsubscribe message:
MarketDepthUnsubscribe { MarketId = "XCME_C ES (M25)" }
MBO Message Handling
After subscribing, the following messages are received:
- MarketDefinition – Sent once per market, unless already received.
- MarketSnapshot – A full order book snapshot.
- MarketOrderUpdate – Incremental order updates.
Example MBO message handling:
private void HandleMBOMessage(ServerMessage serverMessage) { switch (serverMessage.PayloadCase) { case ServerMessage.PayloadOneofCase.MarketDefinition: ProcessMarketDefinition(serverMessage.MarketDefinition); _logger.LogInformation("Received market definition: {MarketId}", serverMessage.MarketDefinition.MarketId); break; case ServerMessage.PayloadOneofCase.MarketSnapshot: ProcessMarketSnapshot(serverMessage.MarketSnapshot); _logger.LogInformation("Received MBO snapshot: {MarketId}", serverMessage.MarketSnapshot.MarketId); break; case ServerMessage.PayloadOneofCase.MarketOrderUpdate: ProcessMarketOrderUpdate(serverMessage.MarketOrderUpdate); _logger.LogInformation("Received MBO order update: {MarketId}", serverMessage.MarketOrderUpdate.MarketId); break; default: _logger.LogWarning("Unhandled MBO Message: {PayloadCase}", serverMessage.PayloadCase); break; } }
Delayed vs. Non-Delayed Data
Clients may receive delayed market data if:
- They have an expired simulator account.
- Their market data entitlements do not allow real-time access.
A flag on the messages indicates whether the data is delayed. Clients should check this flag before displaying market data.
Example MarketDefinition field:
Field | Description |
---|---|
IsDelayed | `true` if the market data is delayed, `false` if real-time. |
If delayed data is received, clients should notify users that the feed is not real-time.