Some systems allow the transmission of real-time quote, order, trade, trade volume, open interest, and/or other price information on a subscription basis. A Market Data Request is a general request for market data on specific securities or forex quotes.
A successful Market Data Request returns one or more Market Data messages containing one or more Market Data Entries. Each Market Data Entry is a Bid, an Offer, a Trade associated with a security, the opening, closing, or settlement price of a security, the buyer or seller imbalance for a security, the value of an index, the trading session high price, low price, or VWAP, or the trade volume or open interest in a security. Market Data Entries usually have a price and a quantity associated with them. For example, in an order book environment, requesting just the top of book will result in only two active Market Data Entries at a time - one for the best Bid and one for the best Offer. For a full book, the Bid and Offer side may each have several Market Data Entries. Each Market Data Entry might represent an aggregate for each price tier, and only one Market Data Entry per side per price would be active at a time. This is referred to as an Aggregated book. When several Market Data Entries at one price tier could each represent a broker, Market Maker, ECN or Exchange's quote in a security, or individual orders in a book, this is a Non-Aggregated book. Alternately, a Market Data Entry could represent a completed trade in a security, the value of an index, the opening, closing, or settlement price of an instrument, the trading session high price, low price, or VWAP, or the volume traded or open interest in a security.
If the message is used for disseminating imbalance information, conventions are as follows:
- MDEntrySize <271> represents the size of the imbalance and is always a positive integer.
- A TradeCondition <277> of either P or Q is required to indicate the side of the imbalance.
- Markets may wish to indicate the presence of an imbalance but not the actual size. In this case, MDEntrySize <271> need not be specified.
One specifies whether a list of trades, a 1-sided or 2-sided book, index, opening, closing, settlement, high, low and VWAP prices and imbalance volumes should be returned by using the NoMDEntryTypes <267> field and MDEntryType <269> repeating group to list all MDEntryType <269> values that should be returned.
Types of Market Data Requests
- A market data feed may consist of both Market Data Snapshot Full Refresh messages and Market Data Incremental Refresh messages.
- The Market Data Request message is used to request a static book snapshot or subscribe to a stream of snapshots and updates.
- Market Data Snapshot Full Refresh should be used to provide a snapshot of the market when Snapshot is requested using SubscriptionRequestType <263>. Use of Market Data Incremental Refresh is being discouraged for this purpose.
- Market Data Snapshot Full Refresh will be used to provide initial snapshot when Snapshot + Updates are requested using SubscriptionRequestType <263>
- The Market Data Request scenarios that will be supported are as follows:
|Component Block - <StandardHeader>||Y||MsgType = V|
|262||MDReqID||Y||Must be unique, or the ID of previous MarketDataRequest <V> to disable if SubscriptionRequestType <263>='2'(Disable previous Snapshot + Updates Request).|
|263||SubscriptionRequestType||Y||SubscriptionRequestType indicates to the other party what type of response is expected. A snapshot request only asks for current information. A subscribe request asks for updates as the status changes. Unsubscribe will cancel any future update messages from the counter party.|
|Component Block - <Parties>||N||Insert here the set of Parties (firm identification) fields defined in "Common Components of Application Messages"|
|265||MDUpdateType||N||Required if SubscriptionRequestType <263>='1'(Snapshot + Updates).|
|286||OpenCloseSettlFlag||N||Can be used to clarify a request if MDEntryType <269>='4'(Opening Price), '5'(Closing Price), or '6'(Settlement Price).|
|546||Scope||N||Defines the scope(s) of the request|
|547||MDImplicitDelete||N||Can be used when MarketDepth <264> >= 2 and MDUpdateType <265> = 1 (Incremental Refresh).|
|Component Block - <MDReqGrp>||Y||Number of MDEntryType fields requested.|
|Component Block - <MarketSegmentScopeGrp>||N||
Can be used to limit the result set to the specified markets or market segments.
|Component Block - <InstrmtMDReqGrp>||Y||Number of symbols (instruments) requested.|
|Component Block - <TrdgSesGrp>||N||Number of trading sessions for which the request is valid.|
|815||ApplQueueAction||N||Action to take if application level queuing exists|
|812||ApplQueueMax||N||Maximum application queue depth that must be exceeded before queuing action is taken.|
|Component Block - <StandardTrailer>||Y|