Indexes

Message Layouts
Session
PreTrade
Trade
PostTrade
Infrastructure

  • Documentation

  • Message

    MarketDataSnapshotFullRefresh (W)

    ID30
    PedigreeAdded FIX.4.2

    The Market Data messages are used as the response to a Market Data Request message. In all cases, one Market Data message refers only to one Market Data Request. It can be used to transmit a 2-sided book of orders or list of quotes, a list of trades, index values, opening, closing, settlement, high, low, or VWAP prices, or any combination of these.

    Market Data messages sent as the result of a Market Data Request message are tagged with the appropriate MDReqID. Unsolicited Market Data messages can be sent; in such cases, MDReqID will not be present.

    If the message is used for foreign exchange, conventions for identifying the forex transaction are as follows:

    • The forex Symbol is defined in "EBS" (Electronic Banking System) format: "CCY1/CCY2".
    • Rates are expressed as "currency1 in currency2" (or "currency2 per currency1") and are calculated as CCY2 divided by CCY1 (NOT CCY1 divided by CCY2)
    • e.g. "GBP/USD" represents a rate expressed as USD per GBP, "USD/JPY" represents a rate expressed as JPY per USD, etc.).
    • CCY1 and CCY2 are ISO currency codes
    • The value of the Currency field represents the denomination of the quantity fields (e.g. JPY represents quantity of JPY).
    • See Appendix O – Foreign Exchange Trading

    Market Data messages include many fields, and not all are required to be used. A firm may, at its option, choose to send the minimum fields required, or may choose to send more information, such as tick direction, tagging of best quotes, etc.

    Market Data messages can take two forms. The first Market Data message format used for a Snapshot, or a Snapshot + Updates where MDUpdateType = Full Refresh (0) is as follows:

    • For Market Data Requests where a Bid or Offer is added, changed, or deleted, every update to a Market Data Entry results in a new Market Data message that contains the entirety of the data requested for that instrument, not just the changed Market Data Entry. In other words, both sides of the market, or just one side in the case of a request of only bids or offers, for the depth requested, must be sent in one FIX Market Data message.
    • A Market Data message may contain several trades, an index value, opening, closing, settlement, high, low, and/or VWAP price for one instrument, but only one instrument per message.
    • Messages containing bids and/or offers cannot contain trades, index value, opening, closing, settlement, high, low, and/or VWAP prices.
    Field
    Name
    Type
    Req'd
    Comments
    Pedigree
    Y
    MsgType = W
    Added FIX.4.2
    262
    Conditionally required if this message is in response to a Market Data Request.
    Added FIX.4.2
    55
    Y
    Added FIX.4.2
    65
    Added FIX.4.2
    48
    Added FIX.4.2
    22
    Added FIX.4.2
    167
    Must be specified if a Future or Option. If a Future: Symbol, SecurityType, and MaturityMonthYear are required. If an Option: Symbol, SecurityType, MaturityMonthYear, PutOrCall, and StrikePrice are required.
    Added FIX.4.2
    200
    For Options or Futures to specify the month and year of maturity.
    Added FIX.4.2
    205
    For Options or Futures and can be used in conjunction with MaturityMonthYear to specify a particular maturity date.
    Added FIX.4.2
    201
    For Options.
    Added FIX.4.2
    202
    For Options.
    Added FIX.4.2
    206
    For Options.
    Added FIX.4.2
    231
    For Fixed Income, Convertible Bonds, Derivatives, etc. Note: If used, quantities should be expressed in the "nominal" (e.g. contracts vs. shares) amount.
    Added FIX.4.2
    223
    For Fixed Income.
    Added FIX.4.2
    207
    Can be used to identify the security.
    Added FIX.4.2
    106
    Added FIX.4.2
    348
    Must be set if EncodedIssuer field is specified and must immediately precede it.
    Added FIX.4.2
    349
    Encoded (non-ASCII characters) representation of the Issuer field in the encoded format specified via the MessageEncoding field.
    Added FIX.4.2
    107
    Added FIX.4.2
    350
    Must be set if EncodedSecurityDesc field is specified and must immediately precede it.
    Added FIX.4.2
    351
    Encoded (non-ASCII characters) representation of the SecurityDesc field in the encoded format specified via the MessageEncoding field.
    Added FIX.4.2
    291
    Added FIX.4.2
    292
    Added FIX.4.2
    387
    Total volume traded in this trading session for this security.
    Added FIX.4.2
    Y
    Number of entries following.
    Added FIX.4.2
    Y
    Added FIX.4.2

    Orchimate Copyright 2026 Atomic Wire Technology Limited
    Orchestra Copyright 2026 FIX Protocol Ltd
    Terms of Service|Privacy Policy