Consolidated Tape for Equities and Bonds CT with FIX Copyright (c) FIX Protocol Ltd. All Rights Reserved. Orchestra v1.0 2026-01-27T20:14:24.701Z int field representing the length in bytes. Value must be positive. int field representing the length in bytes. Value must be positive. Alpha-numeric free format strings, can include any character or punctuation except the delimiter. All String fields are case sensitive (i.e. morstatt != Morstatt). Alpha-numeric free format strings, can include any character or punctuation except the delimiter. All String fields are case sensitive (i.e. morstatt != Morstatt). string field representing a currency type using ISO 4217 Currency code (3 character) values (see Appendix 6-A). string field representing a currency type using ISO 4217 Currency code (3 character) values (see Appendix 6-A). int field representing a message sequence number. Value must be positive. int field representing a message sequence number. Value must be positive. string field representing date and time combination Universal Time Coordinated (UTC), also known as Greenwich Mean Time (GMT). Its value space is described as the combination of date and time of day in the Chapter 5.4 of ISO 8601. Valid values are in the format YYYY-MM-DDTHH:MM:SS.s where YYYY = 0000-9999 year, MM = 01-12 month, DD = 01-31 day, HH = 00-23 hour, MM = 00-59 minute, SS = 00-60 second (60 only if UTC leap second), and optionally one or more digits representing a decimal fraction of a second. The punctuation of "-", ":" and the string value of "T" to separate the date and time are required. The "." is only required when sub-second time precision is specified. Leap Seconds: Note that UTC includes corrections for leap seconds, which are inserted to account for slowing of the rotation of the earth. Leap second insertion is declared by the International Earth Rotation Service (IERS) and has, since 1972, only occurred on the night of Dec. 31 or Jun 30. The IERS considers March 31 and September 30 as secondary dates for leap second insertion, but has never utilized these dates. During a leap second insertion, a UTCTimestamp field may read "1998-12-31T23:59:59", "1998-12-31T23:59:60", "1999-01-01T00:00:00". (see http://tycho.usno.navy.mil/leapsec.html) string field representing time/date combination represented in UTC (Universal Time Coordinated, also known as "GMT") in either YYYYMMDD-HH:MM:SS (whole seconds) or YYYYMMDD-HH:MM:SS.sss* format, colons, dash, and period required. Valid values: YYYY = 0000-9999, MM = 01-12, DD = 01-31, HH = 00-23, MM = 00-59, SS = 00-60 (60 only if UTC leap second), sss* fractions of seconds. The fractions of seconds may be empty when no fractions of seconds are conveyed (in such a case the period is not conveyed), it may include 3 digits to convey milliseconds, 6 digits to convey microseconds, 9 digits to convey nanoseconds, 12 digits to convey picoseconds; Other number of digits may be used with bilateral agreement. Leap Seconds: Note that UTC includes corrections for leap seconds, which are inserted to account for slowing of the rotation of the earth. Leap second insertion is declared by the International Earth Rotation Service (IERS) and has, since 1972, only occurred on the night of Dec. 31 or Jun 30. The IERS considers March 31 and September 30 as secondary dates for leap second insertion, but has never utilized these dates. During a leap second insertion, a UTCTimestamp field may read "19981231-23:59:59", "19981231-23:59:60", "19990101-00:00:00". (see http://tycho.usno.navy.mil/leapsec.html) int field representing the number of entries in a repeating group. Value must be positive. float field representing a price. Note the number of decimal places may vary. For certain asset classes prices may be negative values. For example, prices for options strategies can be negative under certain market conditions. Refer to Volume 7: FIX Usage by Product for asset classes that support negative price values. float field representing a price. Note the number of decimal places may vary. For certain asset classes prices may be negative values. For example, prices for options strategies can be negative under certain market conditions. Refer to Volume 7: FIX Usage by Product for asset classes that support negative price values. float field capable of storing either a whole number (no decimal places) of "shares" (securities denominated in whole units) or a decimal value containing decimal places for non-share quantity asset classes (securities denominated in fractional units). float field capable of storing either a whole number (no decimal places) of "shares" (securities denominated in whole units) or a decimal value containing decimal places for non-share quantity asset classes (securities denominated in fractional units). string field representing a market or exchange using ISO 10383 Market Identifier Code (MIC) values (see"Appendix 6-C). string field representing a market or exchange using ISO 10383 Market Identifier Code (MIC) values (see"Appendix 6-C). Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23"). Single character value, can include any alphanumeric character or punctuation except the delimiter. All char fields are case sensitive (i.e. m != M). Single character value, can include any alphanumeric character or punctuation except the delimiter. All char fields are case sensitive (i.e. m != M). float field typically representing a Price times a Qty float field typically representing a Price times a Qty Values "100" and above are reserved for bilaterally agreed upon user defined enumerations. Values "100" and above are reserved for bilaterally agreed upon user defined enumerations. Values "1000" and above are reserved for bilaterally agreed upon user defined enumerations. Values "1000" and above are reserved for bilaterally agreed upon user defined enumerations. Used to build on and provide some restrictions on what is allowed as valid values in fields that uses a base FIX data type and a pattern data type. The universe of allowable valid values for the field would then be the union of the base set of valid values and what is defined by the pattern data type. The pattern data type used by the field will retain its base FIX data type (e.g. String, int, char). Sequence of digits with optional decimal point and sign character (ASCII characters "-", "0" - "9" and "."); the absence of the decimal point within the string will be interpreted as the float representation of an integer value. All float fields must accommodate up to fifteen significant digits. The number of decimal places used should be a factor of business/market needs and mutual agreement between counterparties. Note that float values may contain leading zeros (e.g. "00023.23" = "23.23") and may contain or omit trailing zeros after the decimal point (e.g. "23.0" = "23.0000" = "23" = "23."). Note that fields which are derived from float may contain negative values unless explicitly specified otherwise. Sequence of digits with optional decimal point and sign character (ASCII characters "-", "0" - "9" and "."); the absence of the decimal point within the string will be interpreted as the float representation of an integer value. All float fields must accommodate up to fifteen significant digits. The number of decimal places used should be a factor of business/market needs and mutual agreement between counterparties. Note that float values may contain leading zeros (e.g. "00023.23" = "23.23") and may contain or omit trailing zeros after the decimal point (e.g. "23.0" = "23.0000" = "23" = "23."). Note that fields which are derived from float may contain negative values unless explicitly specified otherwise. char field containing one of two values: 'Y' = True/Yes 'N' = False/No char field containing one of two values: 'Y' = True/Yes 'N' = False/No Session profile FIX.4.2 Session profile FIX4 Session profile FIXT or LFXIT The choice between FIXT and LFIXT is subject to counterparty agreement. Identifies beginning of new message and session protocol version by means of a session profile identifier (see FIX Session Layer for details). ALWAYS FIRST FIELD IN MESSAGE. (Always unencrypted). Identifies beginning of new message and session protocol version by means of a session profile identifier (see FIX Session Layer for details). ALWAYS FIRST FIELD IN MESSAGE. (Always unencrypted). ISIN Identifies class or source of the SecurityID(48) value. Identifies class or source of the SecurityID(48) value. MarketDataSnapshotFullRefresh MarketDataIncrementalRefresh SecurityStatus TradingSessionStatus Heartbeat The Heartbeat monitors the status of the communication link and identifies when the last of a string of messages was not received. TestRequest The test request message forces a heartbeat from the opposing application. The test request message checks sequence numbers or verifies communication line status. The opposite application responds to the Test Request with a Heartbeat containing the TestReqID. ResendRequest The resend request is sent by the receiving application to initiate the retransmission of messages. This function is utilized if a sequence number gap is detected, if the receiving application lost a message, or as a function of the initialization process. Reject The reject message should be issued when a message is received but cannot be properly processed due to a session-level rule violation. An example of when a reject may be appropriate would be the receipt of a message with invalid basic data which successfully passes de-encryption, CheckSum and BodyLength checks. SequenceReset The sequence reset message is used by the sending application to reset the incoming sequence number on the opposing side. Logout The logout message initiates or confirms the termination of a FIX session. Disconnection without the exchange of logout messages should be interpreted as an abnormal condition. IOI Indication of interest messages are used to market merchandise which the broker is buying or selling in either a proprietary or agency capacity. The indications can be time bound with a specific expiration value. Indications are distributed with the understanding that other firms may react to the message first and that the merchandise may no longer be available due to prior trade. Indication messages can be transmitted in various transaction types; NEW, CANCEL, and REPLACE. All message types other than NEW modify the state of the message identified in IOIRefID. Advertisement Advertisement messages are used to announce completed transactions. The advertisement message can be transmitted in various transaction types; NEW, CANCEL and REPLACE. All message types other than NEW modify the state of a previously transmitted advertisement identified in AdvRefID. ExecutionReport The execution report message is used to: 1. confirm the receipt of an order 2. confirm changes to an existing order (i.e. accept cancel and replace requests) 3. relay order status information 4. relay fill information on working orders 5. relay fill information on tradeable or restricted tradeable quotes 6. reject orders 7. report post-trade fees calculations associated with a trade OrderCancelReject The order cancel reject message is issued by the broker upon receipt of a cancel request or cancel/replace request message which cannot be honored. Logon The logon message authenticates a user establishing a connection to a remote system. The logon message must be the first message sent by the application requesting to initiate a FIX session. News The news message is a general free format message between the broker and institution. The message contains flags to identify the news item's urgency and to allow sorting by subject company (symbol). The News message can be originated at either the broker or institution side, or exchanges and other marketplace venues. Email The email message is similar to the format and purpose of the News message, however, it is intended for private use between two parties. NewOrderSingle The new order message type is used by institutions wishing to electronically submit securities and forex orders to a broker for execution. The New Order message type may also be used by institutions or retail intermediaries wishing to electronically submit Collective Investment Vehicle (CIV) orders to a broker or fund manager for execution. NewOrderList The NewOrderList Message can be used in one of two ways depending on which market conventions are being followed. OrderCancelRequest The order cancel request message requests the cancellation of all of the remaining quantity of an existing order. Note that the Order Cancel/Replace Request should be used to partially cancel (reduce) an order). OrderCancelReplaceRequest The order cancel/replace request is used to change the parameters of an existing order. Do not use this message to cancel the remaining quantity of an outstanding order, use the Order Cancel Request message for this purpose. OrderStatusRequest The order status request message is used by the institution to generate an order status message back from the broker. AllocationInstruction The AllocationInstruction(35=J) message provides the ability to specify how an order or set of orders should be subdivided amongst one or more accounts. ListCancelRequest The List Cancel Request message type is used by institutions wishing to cancel previously submitted lists either before or during execution. ListExecute The List Execute message type is used by institutions to instruct the broker to begin execution of a previously submitted list. This message may or may not be used, as it may be mirroring a phone conversation. ListStatusRequest The list status request message type is used by institutions to instruct the broker to generate status messages for a list. ListStatus The list status message is issued as the response to a List Status Request message sent in an unsolicited fashion by the sell-side. It indicates the current state of the orders within the list as they exist at the broker's site. This message may also be used to respond to the List Cancel Request. AllocationInstructionAck In versions of FIX prior to version 4.4, this message was known as the Allocation ACK message. The Allocation Instruction Ack message is used to acknowledge the receipt of and provide status for an Allocation Instruction message. DontKnowTrade The Don’t Know Trade (DK) message notifies a trading partner that an electronically received execution has been rejected. This message can be thought of as an execution reject message. QuoteRequest In some markets it is the practice to request quotes from brokers prior to placement of an order. The quote request message is used for this purpose. This message is commonly referred to as an Request For Quote (RFQ) Quote The Quote message is used as the response to a Quote Request or a Quote Response message in both indicative, tradeable, and restricted tradeable quoting markets. SettlementInstructions The Settlement Instructions message provides the broker’s, the institution’s, or the intermediary’s instructions for trade settlement. This message has been designed so that it can be sent from the broker to the institution, from the institution to the broker, or from either to an independent "standing instructions" database or matching system or, for CIV, from an intermediary to a fund manager. MarketDataRequest 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 MarketDataRequest(35=V) is a general request for market data on specific securities or forex quotes. The values in the fields provided within the request will serve as further filter criteria for the result set. MarketDataRequestReject The Market Data Request Reject is used when the broker cannot honor the Market Data Request, due to business or technical reasons. Brokers may choose to limit various parameters, such as the size of requests, whether just the top of book or the entire book may be displayed, and whether Full or Incremental updates must be used. QuoteCancel The Quote Cancel message is used by an originator of quotes to cancel quotes. The Quote Cancel message supports cancellation of: • All quotes • Quotes for a specific symbol or security ID • All quotes for a security type • All quotes for an underlying QuoteStatusRequest The quote status request message is used for the following purposes in markets that employ tradeable or restricted tradeable quotes: • For the issuer of a quote in a market to query the status of that quote (using the QuoteID to specify the target quote). • To subscribe and unsubscribe for Quote Status Report messages for one or more securities. MassQuoteAck Mass Quote Acknowledgement is used as the application level response to a Mass Quote message. SecurityDefinitionRequest The SecurityDefinitionRequest(35=c) message is used for the following: 1. Request a specific security to be traded with the second party. The requested security can be defined as a multileg security made up of one or more instrument legs. 2. Request a set of individual securities for a single market segment. 3. Request all securities, independent of market segment. SecurityDefinition The SecurityDefinition(35=d) message is used for the following: 1. Accept the security defined in a SecurityDefinition(35=d) message. 2. Accept the security defined in a SecurityDefinition(35=d) message with changes to the definition and/or identity of the security. 3. Reject the security requested in a SecurityDefinition(35=d) message. 4. Respond to a request for securities within a specified market segment. 5. Convey comprehensive security definition for all market segments that the security participates in. 6. Convey the security's trading rules that differ from default rules for the market segment. SecurityStatusRequest The Security Status Request message provides for the ability to request the status of a security. One or more Security Status messages are returned as a result of a Security Status Request message. TradingSessionStatusRequest The Trading Session Status Request is used to request information on the status of a market. With the move to multiple sessions occurring for a given trading party (morning and evening sessions for instance) there is a need to be able to provide information on what product is trading on what market. MassQuote The Mass Quote message can contain quotes for multiple securities to support applications that allow for the mass quoting of an option series. Two levels of repeating groups have been provided to minimize the amount of data required to submit a set of quotes for a class of options (e.g. all option series for IBM). BusinessMessageReject The Business Message Reject message can reject an application-level message which fulfills session-level rules and cannot be rejected via any other means. Note if the message fails a session-level rule (e.g. body length is incorrect), a session-level Reject message should be issued. BidRequest The BidRequest Message can be used in one of two ways depending on which market conventions are being followed. In the "Non disclosed" convention (e.g. US/European model) the BidRequest message can be used to request a bid based on the sector, country, index and liquidity information contained within the message itself. In the "Non disclosed" convention the entry repeating group is used to define liquidity of the program. See " Program/Basket/List Trading" for an example. In the "Disclosed" convention (e.g. Japanese model) the BidRequest message can be used to request bids based on the ListOrderDetail messages sent in advance of BidRequest message. In the "Disclosed" convention the list repeating group is used to define which ListOrderDetail messages a bid is being sort for and the directions of the required bids. BidResponse The Bid Response message can be used in one of two ways depending on which market conventions are being followed. In the "Non disclosed" convention the Bid Response message can be used to supply a bid based on the sector, country, index and liquidity information contained within the corresponding bid request message. See "Program/Basket/List Trading" for an example. In the "Disclosed" convention the Bid Response message can be used to supply bids based on the List Order Detail messages sent in advance of the corresponding Bid Request message. ListStrikePrice The strike price message is used to exchange strike price information for principal trades. It can also be used to exchange reference prices for agency trades. XMLnonFIX RegistrationInstructions The Registration Instructions message type may be used by institutions or retail intermediaries wishing to electronically submit registration information to a broker or fund manager (for CIV) for an order or for an allocation. RegistrationInstructionsResponse The Registration Instructions Response message type may be used by broker or fund manager (for CIV) in response to a Registration Instructions message submitted by an institution or retail intermediary for an order or for an allocation. OrderMassCancelRequest The order mass cancel request message requests the cancellation of all of the remaining quantity of a group of orders matching criteria specified within the request. NOTE: This message can only be used to cancel order messages (reduce the full quantity). OrderMassCancelReport The Order Mass Cancel Report is used to acknowledge an Order Mass Cancel Request. Note that each affected order that is canceled is acknowledged with a separate Execution Report or Order Cancel Reject message. NewOrderCross Used to submit a cross order into a market. The cross order contains two order sides (a buy and a sell). The cross order is identified by its CrossID. CrossOrderCancelReplaceRequest Used to modify a cross order previously submitted using the New Order - Cross message. See Order Cancel Replace Request for details concerning message usage. CrossOrderCancelRequest Used to fully cancel the remaining open quantity of a cross order. SecurityTypeRequest The Security Type Request message is used to return a list of security types available from a counterparty or market. SecurityTypes The Security Type Request message is used to return a list of security types available from a counterparty or market. SecurityListRequest The Security List Request message is used to return a list of securities from the counterparty that match criteria provided on the request SecurityList The Security List message is used to return a list of securities that matches the criteria specified in a Security List Request. DerivativeSecurityListRequest The Derivative Security List Request message is used to return a list of securities from the counterparty that match criteria provided on the request DerivativeSecurityList The Derivative Security List message is used to return a list of securities that matches the criteria specified in a Derivative Security List Request. NewOrderMultileg The New Order - Multileg is provided to submit orders for securities that are made up of multiple securities, known as legs. MultilegOrderCancelReplace Used to modify a multileg order previously submitted using the New Order - Multileg message. See Order Cancel Replace Request for details concerning message usage. TradeCaptureReportRequest The Trade Capture Report Request can be used to: • Request one or more trade capture reports based upon selection criteria provided on the trade capture report request • Subscribe for trade capture reports based upon selection criteria provided on the trade capture report request. TradeCaptureReport The Trade Capture Report message can be: - Used to report trades between counterparties. - Used to report trades to a trade matching system. - Sent unsolicited between counterparties. - Sent as a reply to a Trade Capture Report Request. - Used to report unmatched and matched trades. OrderMassStatusRequest The order mass status request message requests the status for orders matching criteria specified within the request. QuoteRequestReject The Quote Request Reject message is used to reject Quote Request messages for all quoting models. RFQRequest In tradeable and restricted tradeable quoting markets – Quote Requests are issued by counterparties interested in ascertaining the market for an instrument. Quote Requests are then distributed by the market to liquidity providers who make markets in the instrument. The RFQ Request is used by liquidity providers to indicate to the market for which instruments they are interested in receiving Quote Requests. It can be used to register interest in receiving quote requests for a single instrument or for multiple instruments QuoteStatusReport The quote status report message is used: • as the response to a Quote Status Request message • as a response to a Quote Cancel message • as a response to a Quote Response message in a negotiation dialog (see Volume 7 – PRODUCT: FIXED INCOME and USER GROUP: EXCHANGES AND MARKETS) QuoteResponse The QuoteResponse(35=AJ) message is used for the following purposes: 1. Respond to an IOI(35=6) message 2. Respond to a Quote(35=S) message 3. Counter a Quote 4. End a negotiation dialog 5. Follow-up or end a QuoteRequest(35=R) dialog that did not receive a response. Confirmation The Confirmation messages are used to provide individual trade level confirmations from the sell side to the buy side. In versions of FIX prior to version 4.4, this role was performed by the allocation message. Unlike the allocation message, the confirmation message operates at an allocation account (trade) level rather than block level, allowing for the affirmation or rejection of individual confirmations. PositionMaintenanceRequest The Position Maintenance Request message allows the position owner to submit requests to the holder of a position which will result in a specific action being taken which will affect the position. Generally, the holder of the position is a central counter party or clearing organization but can also be a party providing investment services. PositionMaintenanceReport The Position Maintenance Report message is sent by the holder of a position in response to a Position Maintenance Request and is used to confirm that a request has been successfully processed or rejected. RequestForPositions The Request For Positions message is used by the owner of a position to request a Position Report from the holder of the position, usually the central counter party or clearing organization. The request can be made at several levels of granularity. RequestForPositionsAck The Request for Positions Ack message is returned by the holder of the position in response to a Request for Positions message. The purpose of the message is to acknowledge that a request has been received and is being processed. PositionReport The Position Report message is returned by the holder of a position in response to a Request for Position message. The purpose of the message is to report all aspects of a position and may be provided on a standing basis to report end of day positions to an owner. TradeCaptureReportRequestAck The Trade Capture Request Ack message is used to: - Provide an acknowledgement to a Trade Capture Report Request in the case where the Trade Capture Report Request is used to specify a subscription or delivery of reports via an out-of-band ResponseTransmissionMethod. - Provide an acknowledgement to a Trade Capture Report Request in the case when the return of the Trade Capture Reports matching that request will be delayed or delivered asynchronously. This is useful in distributed trading system environments. - Indicate that no trades were found that matched the selection criteria specified on the Trade Capture Report Request or the Trade Capture Request was invalid for some business reason, such as request is not authorized, invalid or unknown instrument, party, trading session, etc. TradeCaptureReportAck The Trade Capture Report Ack message can be: - Used to acknowledge trade capture reports received from a counterparty. - Used to reject a trade capture report received from a counterparty. AllocationReport Sent from sell-side to buy-side, sell-side to 3rd-party or 3rd-party to buy-side, the AllocationReport(35=AS) message (Claim) provides account breakdown of an order or set of orders plus any additional follow-up front-office information developed post-trade during the trade allocation, matching and calculation phase. AllocationReportAck The Allocation Report Ack message is used to acknowledge the receipt of and provide status for an Allocation Report message. ConfirmationAck The Confirmation Ack (aka Affirmation) message is used to respond to a Confirmation message. SettlementInstructionRequest The Settlement Instruction Request message is used to request standing settlement instructions from another party. AssignmentReport Assignment Reports are sent from a clearing house to counterparties, such as a clearing firm as a result of the assignment process. CollateralRequest An initiator that requires collateral from a respondent sends a Collateral Request. The initiator can be either counterparty to a trade in a two party model or an intermediary such as an ATS or clearinghouse in a three party model. A Collateral Assignment is expected as a response to a request for collateral. CollateralAssignment Used to assign collateral to cover a trading position. This message can be sent unsolicited or in reply to a Collateral Request message. CollateralResponse Used to respond to a Collateral Assignment message. CollateralReport Used to report collateral status when responding to a Collateral Inquiry message. CollateralInquiry Used to inquire for collateral status. NetworkCounterpartySystemStatusRequest This message is send either immediately after logging on to inform a network (counterparty system) of the type of updates required or to at any other time in the FIX conversation to change the nature of the types of status updates required. It can also be used with a NetworkRequestType of Snapshot to request a one-off report of the status of a network (or counterparty) system. Finally this message can also be used to cancel a request to receive updates into the status of the counterparties on a network by sending a NetworkRequestStatusMessage with a NetworkRequestType of StopSubscribing. NetworkCounterpartySystemStatusResponse This message is sent in response to a Network (Counterparty System) Status Request Message. UserRequest This message is used to initiate a user action, logon, logout or password change. It can also be used to request a report on a user's status. UserResponse This message is used to respond to a user request message, it reports the status of the user after the completion of any action requested in the user request message. CollateralInquiryAck Used to respond to a Collateral Inquiry in the following situations: • When the CollateralInquiry will result in an out of band response (such as a file transfer). • When the inquiry is otherwise valid but no collateral is found to match the criteria specified on the Collateral Inquiry message. • When the Collateral Inquiry is invalid based upon the business rules of the counterparty. ConfirmationRequest The Confirmation Request message is used to request a Confirmation message. ContraryIntentionReport The Contrary Intention Report is used for reporting of contrary expiration quantities for Saturday expiring options. This information is required by options exchanges for regulatory purposes. SecurityDefinitionUpdateReport This message is used for reporting updates to a product security master file. Updates could be the result of corporate actions or other business events. Updates may include additions, modifications or deletions. SecurityListUpdateReport The Security List Update Report is used for reporting updates to a Contract Security Masterfile. Updates could be due to Corporate Actions or other business events. Update may include additions, modifications and deletions. AdjustedPositionReport Used to report changes in position, primarily in equity options, due to modifications to the underlying due to corporate actions AllocationInstructionAlert This message is used in a 3-party allocation model (buy-side and sell-side using a central clearing entity) where notification of group creation and group updates to counterparties is needed. The message will also carry trade information that comprised the group to the counterparties. ExecutionAck The Execution Report Acknowledgement message is an optional message that provides dual functionality to notify a trading partner that an electronically received execution has either been accepted or rejected (DK'd). TradingSessionList The Trading Session List message is sent as a response to a Trading Session List Request. The Trading Session List should contain the characteristics of the trading session and the current state of the trading session. TradingSessionListRequest The Trading Session List Request is used to request a list of trading sessions available in a market place and the state of those trading sessions. A successful request will result in a response from the counterparty of a Trading Session List (MsgType=BJ) message that contains a list of zero or more trading sessions. SettlementObligationReport The Settlement Obligation Report message provides a central counterparty, institution, or individual counterparty with a capacity for reporting the final details of a currency settlement obligation. DerivativeSecurityListUpdateReport The Derivative Security List Update Report message is used to send updates to an option family or the strikes that comprise an option family. TradingSessionListUpdateReport The Trading Session List Update Report is used by marketplaces to provide intra-day updates of trading sessions when there are changes to one or more trading sessions. MarketDefinitionRequest The Market Definition Request message is used to request for market structure information from the Respondent that receives this request. MarketDefinition The MarketDefinition(35=BU) message is used to respond to MarketDefinitionRequest(35=BT). In a subscription, it will be used to provide the initial snapshot of the information requested. Subsequent updates are provided by the MarketDefinitionUpdateReport(35=BV). MarketDefinitionUpdateReport In a subscription for market structure information, this message is used once the initial snapshot of the information has been sent using the MarketDefinition(35=BU) message. ApplicationMessageRequest This message is used to request a retransmission of a set of one or more messages generated by the application specified in RefApplID (1355). ApplicationMessageRequestAck This message is used to acknowledge an Application Message Request providing a status on the request (i.e. whether successful or not). This message does not provide the actual content of the messages to be resent. ApplicationMessageReport This message is used for three difference purposes: to reset the ApplSeqNum (1181) of a specified ApplID (1180). to indicate that the last message has been sent for a particular ApplID, or as a keep-alive mechanism for ApplIDs with infrequent message traffic. OrderMassActionReport The Order Mass Action Report is used to acknowledge an Order Mass Action Request. Note that each affected order that is suspended or released or canceled is acknowledged with a separate Execution Report for each order. OrderMassActionRequest The Order Mass Action Request message can be used to request the suspension or release of a group of orders that match the criteria specified within the request. This is equivalent to individual Order Cancel Replace Requests for each order with or without adding "S" to the ExecInst values. It can also be used for mass order cancellation. UserNotification The User Notification message is used to notify one or more users of an event or information from the sender of the message. This message is usually sent unsolicited from a marketplace (e.g. Exchange, ECN) to a market participant. StreamAssignmentRequest In certain markets where market data aggregators fan out to end clients the pricing streams provided by the price makers, the price maker may assign the clients to certain pricing streams that the price maker publishes via the aggregator. An example of this use is in the FX markets where clients may be assigned to different pricing streams based on volume bands and currency pairs. StreamAssignmentReport The StreamAssignmentReport(35=CD) message is in response to the StreamAssignmentRequest(35=CC) message. It provides information back to the aggregator as to which clients to assign to receive which price stream based on requested CCY pair. This message can be sent unsolicited to the Aggregator from the Price Maker. StreamAssignmentReportACK This message is used to respond to the Stream Assignment Report, to either accept or reject an unsolicited assingment. PartyDetailsListRequest The PartyDetailsListRequest is used to request party detail information. PartyDetailsListReport The PartyDetailsListReport message is used to disseminate party details between counterparties. PartyDetailsListReport messages may be sent in response to a PartyDetailsListRequest message or sent unsolicited. MarginRequirementInquiry The purpose of this message is to initiate a margin requirement inquiry for a margin account. The inquiry may be submitted at the detail level or the summary level. It can also be used to inquire margin excess/deficit or net position information. Margin excess/deficit will provide information about the surplus or shortfall compared to the previous trading day or a more recent margin calculation. An inquiry for net position information will trigger one or more PositionReport messages instead of one or more MarginRequirementReport messages. If the inquiry is made at the detail level, an Instrument block must be provided with the desired level of detail. If the inquiry is made at the summary level, the Instrument block is not provided, implying a summary request is being made. For example, if the inquiring firm specifies the Security Type of “FUT” in the Instrument block, then a detail report will be generated containing the margin requirements for all futures positions for the inquiring account. Similarly, if the inquiry is made at the summary level, the report will contain the total margin requirement aggregated to the margin account level. MarginRequirementInquiryAck Used to respond to a Margin Requirement Inquiry. MarginRequirementReport The Margin Requirement Report returns information about margin requirement either as on overview across all margin accounts or on a detailed level due to the inquiry making use of the optional Instrument component block. Application sequencing can be used to re-request a range of reports. PartyDetailsListUpdateReport The PartyDetailsListUpdateReport(35=CK) is used to disseminate updates to party detail information. PartyRiskLimitsRequest The PartyRiskLimitsRequest message is used to request for risk information for specific parties, specific party roles or specific instruments. PartyRiskLimitsReport The PartyRiskLimitsReport message is used to communicate party risk limits. The message can either be sent as a response to the PartyRiskLimitsRequest message or can be published unsolicited. SecurityMassStatusRequest SecurityMassStatus AccountSummaryReport The AccountSummaryReport is provided by the clearinghouse to its clearing members on a daily basis. It contains margin, settlement, collateral and pay/collect data for each clearing member level account type. Clearing member account types will be described through use of the Parties component and PtysSubGrp sub-component. In certain usages, the clearing members can send the AccountSummaryReport message to the clearinghouse as needed. For example, clearing members can send this message to the clearinghouse to identify the value of collateral for each customer (to satisfy CFTC Legally Segregated Operationally Commingled (LSOC) regulatory reporting obligations). Clearing organizations can also send the AccountSummaryReport message to regulators to meet regulatory reporting obligations. For example, clearing organizations can use this message to submit daily reports for each clearing member (“CM”) by house origin and by each customer origin for all futures, options, and swaps positions, and all securities positions held in a segregated account or pursuant to a cross margining agreement, to a regulator (e.g. to the CFTC to meet Part 39, Section 39.19 reporting obligations). PartyRiskLimitsUpdateReport The PartyRiskLimitsUpdateReport(35=CR) is used to convey incremental changes to risk limits. It is similar to the regular report but uses the PartyRiskLimitsUpdateGrp component instead of the PartyRiskLimitsGrp component to include an update action. PartyRiskLimitsDefinitionRequest PartyRiskLimitDefinitionRequest is used for defining new risk limits. PartyRiskLimitsDefinitionRequestAck PartyRiskLimitDefinitionRequestAck is used for accepting (with or without changes) or rejecting the definition of risk limits. PartyEntitlementsRequest The PartyEntitlementsRequest message is used to request for entitlement information for one or more party(-ies), specific party role(s), or specific instruments(s). PartyEntitlementsReport The PartyEntitlementsReport is used to report entitlements for one or more parties, party role(s), or specific instrument(s). QuoteAck The QuoteAck(35=CW) message is used to acknowledge a Quote(35=S) submittal or request to cancel an individual quote using the QuoteCancel(35=Z) message during a Quote/Negotiation dialog. PartyDetailsDefinitionRequest The PartyDetailsDefinitionRequest(35=CX) is used for defining new parties and modifying or deleting existing parties information, including the relationships between parties. The recipient of the message responds with a PartyDetailsDefinitionRequestAck(35=CY) to indicate whether the request was accepted or rejected. PartyDetailsDefinitionRequestAck The PartyDetailsDefinitionRequestAck(35=CY) is used as a response to the PartyDetailsDefinitionRequest(35=CX) message. The request can be accepted (with or without changes) or rejected. PartyEntitlementsUpdateReport The PartyEntitlementsUpdateReport(35=CZ) is used to convey incremental changes to party entitlements. It is similar to the PartyEntitlementsReport(35=CV). This message uses the PartyEntitlementsUpdateGrp component which includes the ability to specify an update action using ListUpdateAction(1324). PartyEntitlementsDefinitionRequest The PartyEntitlementsDefinitionRequest(35=DA) is used for defining new entitlements, and modifying or deleting existing entitlements for the specified party(-ies). PartyEntitlementsDefinitionRequestAck The PartyEntitlementsDefinitionRequestAck(35=DB) is used as a response to the PartyEntitlemensDefinitionRequest(35=DA) to accept (with or without changes) or reject the definition of party entitlements. TradeMatchReport The TradeMatchReport(35=DC) message is used by exchanges and ECN’s to report matched trades to central counterparties (CCPs) as an atomic event. The message is used to express the one-to-one, one-to-many and many-to-many matches as well as implied matches in which more complex instruments can match with simpler instruments. TradeMatchReportAck The TradeMatchReportAck(35=DD) is used to respond to theTradeMatchReport(35=DC) message. It may be used to report on the status of the request (e.g. accepting the request or rejecting the request). PartyRiskLimitsReportAck PartyRiskLimitsReportAck is an optional message used as a response to the PartyRiskLimitReport(35=CM) or PartyRiskLimitUpdateReport(35=CR) messages to acknowledge or reject those messages. PartyRiskLimitCheckRequest PartyRiskLimitCheckRequest is used to request for approval of credit or risk limit amount intended to be used by a party in a transaction from another party that holds the information. PartyRiskLimitCheckRequestAck PartyRiskLimitCheckRequestAck is used to acknowledge a PartyRiskLimitCheckRequest(35=DF) message and to respond whether the limit check request was approved or not. When used to accept the PartyRiskLimitCheckRequest(35=DF) message the Respondent may also include the limit amount that was approved. PartyActionRequest The PartyActionRequest message is used suspend or halt the specified party from further trading activities at the Respondent. The Respondent must respond with a PartyActionReport(35=DI) message. PartyActionReport Used to respond to the PartyActionRequest(35=DH) message, indicating whether the request has been received, accepted or rejected. Can also be used in an unsolicited manner to report party actions, e.g. reinstatements after a manual intervention out of band. MassOrder The MassOrder(35=DJ) message can be used to add, modify or delete multiple unrelated orders with a single message. Apart from clearing related attributes, only the key order attributes for high performance trading are available. MassOrderAck The mass order acknowledgement message is used to acknowledge the receipt of and the status for a MassOrder(35=DJ) message. PositionTransferInstruction The PositionTransferInstruction(35=DL) is sent by clearing firms to CCPs to initiate position transfers, or to accept or decline position transfers. PositionTransferInstructionAck The PositionTransferInstructionAck(35=DM) is sent by CCPs to clearing firms to acknowledge position transfer instructions, and to report errors processing position transfer instructions. PositionTransferReport The PositionTransferReport(35=DN) is sent by CCPs to clearing firms indicating of positions that are to be transferred to the clearing firm, or to report on status of the transfer to the clearing firms involved in the transfer process. MarketDataStatisticsRequest The MarketDataStatisticsRequest(35=DO) is used to request for statistical data. The simple form is to use an identifier (MDStatisticID(2475)) assigned by the market place which would denote a pre-defined statistical report. Alternatively, or also in addition, the request can define a number of parameters for the desired statistical information. MarketDataStatisticsReport The MarketDataStatisticsReport(35=DP) is used to provide unsolicited statistical information or in response to a specific request. Each report contains a set of statistics for a single entity which could be a market, a market segment, a security list or an instrument. CollateralReportAck CollateralReportAck(35=DQ) is used as a response to the CollateralReport(35=BA). It can be used to reject a CollateralReport(35=BA) when the content of the report is invalid based on the business rules of the receiver. The message may also be used to acknowledge receipt of a valid CollateralReport(35=BA). MarketDataReport The MarketDataReport(35=DR) message is used to provide delimiting references (e.g. start and end markers in a continuous broadcast) and details about the number of market data messages sent in a given distribution cycle. CrossRequest The CrossRequest(35=DS) message is used to indicate the submission of orders or quotes that may result in a crossed trade. CrossRequestAck The CrossRequestAck(35=DT) message is used to confirm the receipt of a CrossRequest(35=DS) message. AllocationInstructionAlertRequest This message is used in a clearinghouse 3-party allocation model to request for AllocationInstructionAlert(35=BM) from the clearinghouse. The request may be used to obtain a one-time notification of the status of an allocation group. AllocationInstructionAlertRequestAck This message is used in a clearinghouse 3-party allocation model to acknowledge a AllocationInstructionAlertRequest(35=DU) message for an AllocationInstructionAlert(35=BM) message from the clearinghouse. TradeAggregationRequest TradeAggregationRequest(35=DW) is used to request that the identified trades between the initiator and respondent be aggregated together for further processing. TradeAggregationReport TradeAggregationReport(35=DX) is used to respond to the TradeAggregationRequest(35=DW) message. It provides the status of the request (e.g. accepted or rejected) and may also provide additional information supplied by the respondent. PayManagementReport PayManagementReport(35=EA) may be used to respond to the PayManagementRequest(35=DY) message. It provides the status of the request (e.g. accepted, disputed) and may provide additional information related to the request. PayManagementReport(35=EA) may also be sent unsolicited by the broker to a client. In which case the client may acknowledge and resolve disputes out-of-band or with a simple PayManagementReportAck(35=EB). PayManagementReport(35=EA) may also be sent unsolicited to report the progress status of the payment itself with PayReportTransType(2804)=2 (Status). PayManagementReportAck PayManagementReportAck(35=EB) is used as a response to the PayManagementReport(35=EA) message. It may be used to accept, reject or dispute the details of the PayManagementReport(35=EA) depending on the business rules of the receiver. This message may also be used to acknowledge the receipt of a PayManagementReport(35=EA) message. PayManagementRequest PayManagementRequest(35=DY) message is used to communicate a future or expected payment to be made or received related to a trade or contract after its settlement. PayManagementRequestAck PayManagementRequestAck(35=DZ) is used to acknowledge the receipt of the PayManagementRequest(35=DY) message (i.e. a technical acknowledgement of receipt). Acceptance or rejection of the request is reported in the corresponding PayManagementReport(35=EA). SettlementStatusRequest SettlementStatusRequest(35=EC) is used to request for the settlement status of a trade. SettlementStatusRequestAck SettlementStatusRequestAck(35=ED) is used to respond to the SettlementStatusRequest(35=EC) to acknowledge the request and provide status for the request message. SettlementStatusReport SettlementStatusReport(35=EE) is a response to the SettlementStatusRequest(35=EC) to provide settlement status for the requested trade. It may also be sent unsolicited without an explicit request message by the party able to provide the settlement status for the trade identified in the report message. SettlementStatusReportAck SettlementStatusReportAck(35=EF) is used to respond to the SettlementStatusReport(35=EE) to acknowledge or reject the report. SecurityRiskMetricsReport SecurityRiskMetricsReport(35=EG) is used for publishing the risk metrics, valuation metrics or analytics of one or more securities, or for an option series. AlgoCertificateRequest AlgoCertificateRequest(35=EH) is used to request algo testing certificate information for one or more algorithms. AlgoCertificateRequestAck AlgoCertificateRequestAck(35=EI) is used to respond to the AlgoCertificateRequest(35=EH) to acknowledge the request and provide status for the request message. AlgoCertificateReport AlgoCertificateReport(35=EJ) is a response to the AlgoCertificateRequest(35=EH) to certify an algo. It may also be sent unsolicited without an explicit request message by the party able to provide certificate information for the algo identified in the report message. AlgoCertificateReportAck AlgoCertificateReportAck(35=EK) is used to respond to the AlgoCertificateReport(35=EJ) to acknowledge or reject the report message. TestSuiteDefinitionRequest TestSuiteDefinitionRequest(35=EL) is used to convey to the test system the suite of test scenarios to perform. TestSuiteDefinitionRequestAck TestSuiteDefinitionRequestAck(35=EM) is used to respond to the TestSuiteDefinitionRequest(35= EL) to acknowledge the request and provide status for the request message. TestActionRequest TestActionRequest(35=EN) is used to manage test executions or request for testing activity state of the identified test suite. TestActionRequestAck TestActionRequestAck(35=EO) is used to respond to the TestActionRequest(35=EN) to acknowledge the request and provide status for the request message. TestActionReport TestActionReport(35=EP) is used to report the testing results of the identified test suite that has been executed with TestActionRequest(35=EN). In the context of algorithmic trading, the results may be used to create a certificate for the algorithm upon meeting the success criteria. MarketDataAck This message may be used as a response to the MarketDataSnapshotFullRefresh(35=W) and MarketDataIncrementalRefresh(35=X) messages. SecurityStatusAck This message may be used as a response to the SecurityStatus(35=f) message. TradingSessionStatusAck This message may be used as a response to the TradingSessionStatus(35=h) message. Defines message type ALWAYS THIRD FIELD IN MESSAGE. (Always unencrypted) Note: A "U" as the first character in the MsgType field (i.e. U, U2, etc) indicates that the message format is privately defined between the sender and receiver. *** Note the use of lower case letters *** Bid Offer Trade Auction clearing price Empty book Type of market data entry. Type of market data entry. Trade Type of market data entry. Type of market data entry. Bid Offer Empty book Type of market data entry. Type of market data entry. Auction clearing price Empty book Type of market data entry. Type of market data entry. Bid Use for Side BUYI. Offer Use for Side SELL. Auction clearing price Empty book Type of market data entry. Type of market data entry. New Change Use for flag AMND. Delete Use for flag CANC. Type of Market Data update action. Type of Market Data update action. Day Identifier for a trading session. A trading session spans an extended period of time that can also be expressed informally in terms of the trading day. Usage is determined by market or counterparties. To specify good for session where session spans more than one calendar day, use TimeInForce = 0 (Day) in conjunction with TradingSessionID(336). Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility. Identifier for a trading session. A trading session spans an extended period of time that can also be expressed informally in terms of the trading day. Usage is determined by market or counterparties. To specify good for session where session spans more than one calendar day, use TimeInForce = 0 (Day) in conjunction with TradingSessionID(336). Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility. Unknown Open Use for ACTV. Outage Use for OTAG. Partial outage Use for POTG. State of the trading session. State of the trading session. Percentage (i.e. percent of par) Use for PERC. Fixed amount (absolute value) Use for MONE. Yield Use for YIEL. Basis points Use for BAPO. Code to represent the price type. Code to represent the price type. Market Identifier Code (ISO 10383) MIC - Use for trading venues and APAs that have a MIC. Generally accepted market participant identifier - Use for APAs that do not have a MIC. Identifies class or source of the PartyID (448) value. Required if PartyID is specified. Note: applicable values depend upon PartyRole (452) specified. Report originator Use for Venue of Publication. Execution Venue Use for Third-Country Trading Venue of Execution. Identifies the type or role of the PartyID (448) specified. Identifies the type or role of the PartyID (448) specified. Report originator Use for Venue of Publication. Identifies the type or role of the PartyID (448) specified. Identifies the type or role of the PartyID (448) specified. One-Party Trade Report (privately negotiated trade) Use for TROF. Confirmed Trade Report (reporting from recognized markets) Use for TROE. Systematic Internaliser (SI) Use for TRSI. The point in the matching process at which this trade was matched. Opening or opening auction Use for SOAU. (Continuous) Trading Use for COTR. Closing or closing auction Use for SCAU. Post-Trading Use for MACT. Scheduled intraday auction Use for SIAU. Any auction Use for UDUC. Unscheduled intraday auction Use for UAUC. Out of main session trading Use for OMST. Order initiated auction Use for ODAU. Other Use for OTSP. Optional market assigned sub identifier for a trading phase within a trading session. Usage is determined by market or counterparties. Used by US based futures markets to identify exchange specific execution time bracket codes as required by US market regulations. Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility Order initiated auction Use for ODAU. Optional market assigned sub identifier for a trading phase within a trading session. Usage is determined by market or counterparties. Used by US based futures markets to identify exchange specific execution time bracket codes as required by US market regulations. Bilaterally agreed values of data type "String" that start with a character can be used for backward compatibility Execution time Use for Trading Date and Time (venue). Time in Use for "Date and Time when the data contributor received the data" (APA). Publicly reported Use for "Publication Date and Time of the data contributor" (venue or APA). Trading / Regulatory timestamp type. Note of applicability: Values are required in various regulatory environments: required for US futures markets to support computerized trade reconstruction, required by MiFID II / MiFIR for transaction reporting and publication, required by FINRA for reporting to the Consolidated Audit Trail (CAT), and required by SEC for recordkeeping requirements in the context of T+1. Execution time Use for Trading Date and Time (venue). Time in Use for Reception Date and Time (CTP). Publicly reported Use for Publication Date and Time (venue/APA or CTP). Trading / Regulatory timestamp type. Note of applicability: Values are required in various regulatory environments: required for US futures markets to support computerized trade reconstruction, required by MiFID II / MiFIR for transaction reporting and publication, required by FINRA for reporting to the Consolidated Audit Trail (CAT), and required by SEC for recordkeeping requirements in the context of T+1. Orderbook entry time Use for Update Date and Time of non-aggregated orderbooks (venue). Publicly reported Use for "Publication Date and Time of the data contributor" (venue or APA). Update time Use for Update Date and Time of aggregated orderbooks or auctions (venue). Trading / Regulatory timestamp type. Note of applicability: Values are required in various regulatory environments: required for US futures markets to support computerized trade reconstruction, required by MiFID II / MiFIR for transaction reporting and publication, required by FINRA for reporting to the Consolidated Audit Trail (CAT), and required by SEC for recordkeeping requirements in the context of T+1. Publicly reported Use for Publication Data and Time (venue) and Dissemination Date and Time (CTP). Reference time for BBO Use for EBBO timestamp (CTP). Update time Use for Entry Date and Time (venue). Trading / Regulatory timestamp type. Note of applicability: Values are required in various regulatory environments: required for US futures markets to support computerized trade reconstruction, required by MiFID II / MiFIR for transaction reporting and publication, required by FINRA for reporting to the Consolidated Audit Trail (CAT), and required by SEC for recordkeeping requirements in the context of T+1. Publicly reported Use for Publication Date and Time (venue). Update time Use for Indicative Date and Time (venue). Trading / Regulatory timestamp type. Note of applicability: Values are required in various regulatory environments: required for US futures markets to support computerized trade reconstruction, required by MiFID II / MiFIR for transaction reporting and publication, required by FINRA for reporting to the Consolidated Audit Trail (CAT), and required by SEC for recordkeeping requirements in the context of T+1. Execution time Use for Trading Date and Time (venue). Publicly reported Use for "Publication Date and Time of the data contributor" (venue or APA). Trading / Regulatory timestamp type. Note of applicability: Values are required in various regulatory environments: required for US futures markets to support computerized trade reconstruction, required by MiFID II / MiFIR for transaction reporting and publication, required by FINRA for reporting to the Consolidated Audit Trail (CAT), and required by SEC for recordkeeping requirements in the context of T+1. Contributor Use for data contributor (venue/APA). Publisher Use for data publisher (CTP). Contributor Use for data contributor (venue/APA). Exchange for physical (EFP) Use for XFPH. Privately negotiated trade Use for NEGO. Portfolio trade Use for PORT. Benchmark Use for BENC. Package trade Use for CONT and TPAC (mutually exclusive). Portfolio trade Use for PORT. Benchmark Use for BENC. Package trade Use for CONT. Exchange for physical (EFP) Use for XFPH. Package trade Use for TPAC. Benchmark Use for BENC. Portfolio trade Use for PORT. Exchange for physical (EFP) Use for XFPH. Privately negotiated trade Use for NEGO. Package trade Use for TPAC. Benchmark Use for BENC. Portfolio trade Use for PORT. Units (shares, par, currency) Type of quantity specified in quantity field. ContractMultiplier (tag 231) is required when QtyType = 1 (Contracts). UnitOfMeasure (tag 996) and TimeUnit (tag 997) are required when QtyType = 2 (Units of Measure per Time Unit). Active Use for ACTV when there is no previous status. Delisted Use for RMOV. Suspended Use for SUSP. Indicates the current state of the instrument. Indicates the current state of the instrument. Price Depth Use for aggregated orderbooks. Order Depth Use for non-aggregated orderbooks. Describes the type of book for which the feed is intended. Used when multiple feeds are provided over the same connection Book Use for CLOB. Quote driven market Use for QDTS. Auction driven market Use for PATS. Quote negotiation Use for RFQT. Voice negotiation Use for VOIC. Hybrid market Use for HYBR. Other market Use for OTHR. Used to describe the origin of the market data entry. Book Use for Trading System CLOB. Auction driven market Use for PATS. Used to describe the origin of the market data entry. Book Use for CLOB. Quote driven market Use for QDTS. Auction driven market Use for PATS. Quote negotiation Use for RFQT. Hybrid market Use for HYBR. Other market Use for OTHR. Used to describe the origin of the market data entry. Book Use for CLOB. Quote driven market Use for QDTS. Auction driven market Use for PATS. Quote negotiation Use for RFQT. Voice negotiation Use for VOIC. Hybrid market Use for HYBR. Other market Use for OTHR. Used to describe the origin of the market data entry. Central limit order book Use for CLOB. Quote driven market Use for QDTS. Auction driven market Use for PATS. Quote negotiation Use for RFQT. Voice negotiation Use for VOIC. Hybrid market Use for HYBR. Other market (lowercase "z") Use for OTHR. Identifies the type of venue where a trade was executed. Central limit order book Use for CLOB. Quote driven market Use for QDTS. Auction driven market Use for PATS. Quote negotiation Use for RFQT. Hybrid market Use for HYBR. Other market (lowercase "z") Use for OTHR. Identifies the type of venue where a trade was executed. Central limit order book Use for CLOB. Quote driven market Use for QDTS. Auction driven market Use for PATS. Quote negotiation Use for RFQT. Voice negotiation Use for VOIC. Hybrid market Use for HYBR. Other market (lowercase "z") Use for OTHR. Identifies the type of venue where a trade was executed. Special dividend Use for SDIV. Non-price forming trade Use for NPFT. Price is pending Use for PNDG. Price is not applicable Use for NOAP. Price conditions in effect at the time of the trade. Multiple price conditions can be in effect at the same time. Price conditions are usually required to be reported in markets that have regulations on price execution at a market or national best bid or offer, and the trade price differs from the best bid or offer. Special dividend Use for SDIV. Non-price forming trade Use for NPFT. Price is pending Use for PNDG. Price is not applicable Use for NOAP. Price conditions in effect at the time of the trade. Multiple price conditions can be in effect at the same time. Price conditions are usually required to be reported in markets that have regulations on price execution at a market or national best bid or offer, and the trade price differs from the best bid or offer. Non-price forming trade Use for NPFT. Price is pending Use for PNDG. Price is not applicable Use for NOAP. Price conditions in effect at the time of the trade. Multiple price conditions can be in effect at the same time. Price conditions are usually required to be reported in markets that have regulations on price execution at a market or national best bid or offer, and the trade price differs from the best bid or offer. Price is pending Use for PNDG. Price is not applicable Use for NOAP. Price conditions in effect at the time of the trade. Multiple price conditions can be in effect at the same time. Price conditions are usually required to be reported in markets that have regulations on price execution at a market or national best bid or offer, and the trade price differs from the best bid or offer. Volume Omission Trade Use for OMIS. Four Weeks Aggregation Trade Use for AGFW. Full Details of "Volume Omission Trade" Use for FULO. Full Details of "Four Weeks Aggregation Trade" Use for FULG. Type of regulatory report. Volume Omission Trade Use for OMIS. Full Details of "Volume Omission Trade" Use for FULO. Four Weeks Aggregation Trade Use for AGFW. Full Details of "Four Weeks Aggregation Trade" Use for FULG. Type of regulatory report. Volume Omission Trade Use for VOLO. Full Details of "Volume Omission Trade" Use for FULV. Type of regulatory report. Non-algorithmic trade Algorithmic trade Use for ALGO. Indicates that the order or trade originates from a computer program or algorithm requiring little-to-no human intervention. Indicates that the order or trade originates from a computer program or algorithm requiring little-to-no human intervention. Pre-trade transparency waiver Use for NLIQ, OILQ, PRIC, RFPT, NTLS (only input for equities). Post-trade deferral Use for LRGS, ILQD, SIZE, MLF1, MLF2, LLF3, LLF4, VLF5, VLF6. Specifies the type of regulatory trade publication. Additional reasons for the publication type may be specified in TrdRegPublicationReason(2670). Specifies the type of regulatory trade publication. Additional reasons for the publication type may be specified in TrdRegPublicationReason(2670). Post-trade deferral Specifies the type of regulatory trade publication. Additional reasons for the publication type may be specified in TrdRegPublicationReason(2670). Specifies the type of regulatory trade publication. Additional reasons for the publication type may be specified in TrdRegPublicationReason(2670). Pre-trade transparency waiver Use for NLIQ, OILQ, PRIC, RFPT. Post-trade deferral Use for LRGS. Specifies the type of regulatory trade publication. Additional reasons for the publication type may be specified in TrdRegPublicationReason(2670). Specifies the type of regulatory trade publication. Additional reasons for the publication type may be specified in TrdRegPublicationReason(2670). No preceding order in book as transaction price set within average spread of a liquid instrument Use for NLIQ. No preceding order in book as transaction price depends on system-set reference price for an illiquid instrument Use for OILQ. No preceding order in book as transaction price is for transaction subject to conditions other than current market price Use for PRIC. No public price for preceding order as public reference price was used for matching orders Use for RFPT. Deferral due to "Large in Scale" Use for LRGS. Deferral due to "Illiquid Instrument" Publication deferral is permitted if the transaction's instrument is illiquid, as defined by regulator's stipulation. For ESMA RTS 2, this is the "ILQD" flag. Deferral due to "Size Specific" Per MiFIR Article 11, publication deferral is permitted if the transaction is greater than the stipulated 'Size Specific to the financial instrument' threshold. For ESMA RTS 2, this is the "SIZE" flag. Deferral due to medium liquid instrument Use for MLF1. Deferral due to medium illiquid instrument Use for MIF2. Deferral due to large liquid instrument Use for LLF3. Deferral due to large illiquid instrument Use for LIF4. Deferral due to very large liquid instrument Use for VLF5. Deferral due to very large illiquid instrument Use for VIF5. Deferral for ETCs, ETNs, SFPs and emission allowances Use for DEFF. Additional reason for trade publication type specified in TrdRegPublicationType(2669). Reasons may be specific to regulatory trade publication rules. Deferral due to medium liquid instrument Use for MLF1. Deferral due to medium illiquid instrument Use for MIF2. Deferral due to large liquid instrument Use for LLF3. Deferral due to large illiquid instrument Use for LIF4. Deferral due to very large liquid instrument Use for VLF5. Deferral due to very large illiquid instrument Use for VIF5. Additional reason for trade publication type specified in TrdRegPublicationType(2669). Reasons may be specific to regulatory trade publication rules. No preceding order in book as transaction price set within average spread of a liquid instrument Use for NLIQ. No preceding order in book as transaction price depends on system-set reference price for an illiquid instrument Use for OILQ. No preceding order in book as transaction price is for transaction subject to conditions other than current market price Use for PRIC. No public price for preceding order as public reference price was used for matching orders Use for RFPT. Deferral due to "Large in Scale" Use for LRGS. Additional reason for trade publication type specified in TrdRegPublicationType(2669). Reasons may be specific to regulatory trade publication rules. Deferral due to "Large in Scale" Use for LRGS. Additional reason for trade publication type specified in TrdRegPublicationType(2669). Reasons may be specific to regulatory trade publication rules. No data quality issue Data quality issue Accepted Rejected Accepted with errors Indicates the status of a report. Trading halt Use for HALT. Resume Use for ACTV when previous state was SUSP, RMOV or HALT. Unknown or Invalid Identifies the trading status applicable to the transaction. Trading venue transaction identifier Specifies the type of trade identifier provided in RegulatoryTradeID(1903). Contextual hierarchy of events for the same trade or transaction maybe captured through use of the different RegulatoryTradeIDType(1906) values using multiple instances of the repeating group as needed for regulatory reporting. Cross as principal Use for flag MTCH. Identifies role of dealer; Agent, Principal, RisklessPrincipal Identifies beginning of new message and session protocol version by means of a session profile identifier (see FIX Session Layer for details). ALWAYS FIRST FIELD IN MESSAGE. (Always unencrypted). Message length, in bytes, forward to the CheckSum field. ALWAYS SECOND FIELD IN MESSAGE. (Always unencrypted) Three byte, simple checksum (see Volume 2: "Checksum Calculation" for description). ALWAYS LAST FIELD IN MESSAGE; i.e. serves, with the trailing <SOH>, as the end-of-message delimiter. Always defined as three characters. (Always unencrypted) Use for Currency. Required by FIX when SecurityID(48) is used. Use for Venue of Execution (set to XOFF when execution is at Third-Country Trading Venue of Execution). Identifies number of lines of text body Integer message sequence number. Defines message type ALWAYS THIRD FIELD IN MESSAGE. (Always unencrypted) Note: A "U" as the first character in the MsgType field (i.e. U, U2, etc) indicates that the message format is privately defined between the sender and receiver. *** Note the use of lower case letters *** Use for Instrument Identification Code. Assigned value used to identify firm sending message. Time of message transmission (always expressed in UTC (Universal Time Coordinated, also known as "GMT") Required when using FIX TagValue encoding (ISO 3531-1) and Instrument component is marked as required. Set to "[N/A]" in such a case. Assigned value used to identify receiving firm. Free format text string. Use for Dissemination Date and Time. Use for Instrument/System Status Start Date and Time. Number of entries in Market Data message. Type of market data entry. Type of market data entry. Type of market data entry. Type of market data entry. Type of market data entry. Use for Price. Conditionally required unless flag PNDG or NOAP is set (see TradePriceCondition(1839)). Quantity or volume represented by the Market Data Entry. Use for flags to amend or cancel a previously reported transaction. Equivalent to MMT Level 3.4 (Modification Indicator) for Transaction Type. Use for Instrument Status (except SUSP or RMOV). Use for Highest Auction Price. Use for Lowest Auction Price. Conditionally required by FIX when TradingSessionSubID(625) is present. Use for Trading System Status. Total amount traded expressed in units of currency - usually quantity * price. For FX Futures this is used to express the notional value of a fill when quantity fields are expressed in terms of contract size (i.e. quantity * price * contract size). Use for Price Notation. Required by FIX when PartyID(448) is used. Use for Third-Country Trading Venue of Execution (only when LastMkt(30)=XOFF) and for Venue of Publication. Required by FIX when PartyID(448) is used. Required by FIX when PartyID(448) is used. Number of PartyID (448), PartyIDSource (447), and PartyRole (452) entries Use for subset of Trading System Phase. Equivalent to MMT Level 2 - Trading Mode. Mutually exclusive with TradingSessionSubID(625). Use for subset of Trading System Phase. Equivalent to MMT Level 2 - Trading Mode. Mutually exclusive with MatchType(574). Use for subset of Trading System Phase. Equivalent to MMT Level 2 - Trading Mode. Number of timestamp entries. Use for timestamp together with TrdRegTimestampType(770) and TrdRegTimestampOrigin(771). Required by FIX when TrdRegTimestamp(769) is used. Required by FIX when TrdRegTimestamp(769) is used. Required by FIX when TrdRegTimestamp(769) is used. Required by FIX when TrdRegTimestamp(769) is used. Required by FIX when TrdRegTimestamp(769) is used. Required by FIX when TrdRegTimestamp(769) is used. Use to distinguish timestamps from data contributors and data publishers. Use to distinguish timestamps from data contributors and data publishers. Type of quantity specified in quantity field. ContractMultiplier (tag 231) is required when QtyType = 1 (Contracts). UnitOfMeasure (tag 996) and TimeUnit (tag 997) are required when QtyType = 2 (Units of Measure per Time Unit). Use for Instrument Status (except HALT). Describes the type of book for which the feed is intended. Used when multiple feeds are provided over the same connection Use for Trading System Type. Equivalent to MMT Level 1 - Market Mechanism. Omit when LastMkt(30)=SINT or XOFF. Use for Trading System Type. Equivalent to MMT Level 1 - Market Mechanism. Omit when LastMkt(30)=SINT or XOFF. Use for Trading System Type. Equivalent to MMT Level 1 - Market Mechanism. Omit when LastMkt(30)=SINT or XOFF. Use for Trading System Type. Equivalent to MMT Level 1 - Market Mechanism. Omit when LastMkt(30)=SINT or XOFF. Use when message sent by CTP is based on out-of-band communication with the data contributor. In exceptional circumstances, a CTP must delete and amend information in a trade report on request from the entity providing the information when that entity cannot delete or amend its own information for technical reasons. Use for flag MTCH. Equivalent to MMT Level 3.3 Transaction Type (Agency Cross Trade Indicator). Use for (Trading) Venue. Identifies the reason for rejection. Use for Trading System Type. Use for Trading System Type. Use for Trading System Type. Number of trade price conditions. Use for subset of the post-trade transparency flags and for Missing Price. Equivalent to MMT Level 3.8 (Trades Outside Price Formation/Discovery Process) for Transaction Type. Use for subset of the post-trade transparency flags and for Missing Price. Equivalent to MMT Level 3.6 (Special Dividend Indicator) and 3.8 (Trades Outside Price Formation/Discovery Process) for Transaction Type. Use for subset of the post-trade transparency flags and for Missing Price. Equivalent to MMT Level 3.8 (Trades Outside Price Formation/Discovery Process) for Transaction Type. Use for Transaction Identification Code. Specifies the type of trade identifier provided in RegulatoryTradeID(1903). Contextual hierarchy of events for the same trade or transaction maybe captured through use of the different RegulatoryTradeIDType(1906) values using multiple instances of the repeating group as needed for regulatory reporting. Number of regulatory IDs in the repeating group. Use for supplementary deferral flags. Equivalent to MMT Level 4.2 for Post-Trade Deferral or Enrichment Type. Use for supplementary deferral flags. Equivalent to MMT Level 4.2 for Post-Trade Deferral or Enrichment Type. Use for supplementary deferral flags. Equivalent to MMT Level 4.2 for Post-Trade Deferral or Enrichment Type. Use for post-trade transparency flag ALGO. Equivalent to MMT Level 3.9 (Algorithmic Indicator) for Transaction Type. Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Use for subset of the post-trade transparency flags. Use for subset of the post-trade transparency flags. Equivalent to MMT Level 4.1 for Post-Trade Deferral Reason. Use for subset of the pre- and post-trade transparency flags. Equivalent to MMT Level 3.2 (Pre-Trade Transparency Waiver), 3.5 (Reference Price Indicator), and 3.10 (Pre-Trade Transparency Waiver Related to Size/Scale) for TransactionTypes and Level 4.1 for Post-Trade Deferral Reason. Use for subset of the post-trade transparency flags. Number of trade types in repeating group. Use for subset of the post-trade transparency flags. Use for subset of the post-trade transparency flags. Equivalent to MMT Level 3.1 (Transaction Category), 3.2 (Negotiation Indicator), 3.5 (Benchmark), and 3.11 (Portfolio) for TransactionTypes. Use for subset of the post-trade transparency flags. Equivalent to MMT Level 3.5 (Benchmark), 3.11 (Portfolio), and 3.12 (Contingent) for TransactionTypes. Use for subset of the post-trade transparency flags. Equivalent to MMT Level 3.1 (Transaction Category), 3.2 (Negotiation Indicator), 3.5 (Benchmark), and 3.11 (Portfolio) for TransactionTypes. Identifies the most liquid market for an instrument. In the context of the EU Consolidated Tape, this is used to identify the most relevant market in terms of liquidity. Identifies whether a given market is the most liquid for a given instrument. In the context of the EU Consolidated Tape, this is used to indicate whether a given market is the most relevant market in terms of liquidity (MRMTL). Use for Number of Transactions. Number of trades included in a given trade. In the context of the EU Consolidated Tape, this is used for the deferred publication of trades as a single, aggregated trade. Indicates the quality of the market data being provided. In the context of the EU Consolidated Tape, this is used by the CTP to identify suspicious data coming from the data contributor. Unique message identifier. Conditionally required when supporting MarketDataAck(35=EQ) as response message. Indicates the status of a report. Use for Instrument Identification Code Type. Required by FIX when SecurityID(48) is used. (Always unencrypted, always last field in message) Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Use for Venue of Publication. Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Specifies the number of repeating lines of text. Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Use for Side (input). Use for Price (input), Best Bid (Output), Best Offer (output), Volume Weighted Auction Price (output). Use for Price Currency (input) and Currency (output). Use for Quantity (input), Best Bid Volume (output), Best Offer Volume (output), Auction Volume (output). Required when using FIX TagValue encoding (ISO 3531-1). Use for Side or set to Q when Side is absent, i.e. auction information is provided. Set to J=Empty book to remove bid and offer information. Use for Price. Use for Price Currency. Use for Quantity. Use for subset of Trading System Phase. Equivalent to MMT Level 2 - Trading Mode. Use for Trading System Type. Equivalent to MMT Level 1 - Market Mechanism. Required when using FIX TagValue encoding (ISO 3531-1). Set to 0=Bid for Best Bid and Best Bid Volume and set to 1=Offer for Best Offer and Best Offer Volume. Set to J=Empty book to remove bid and offer information. Use for Best Bid and Best Offer. Use for Currency. Use for Best Bid Volume and Best Offer Volume. The repeating group requires two entries, one for the bid and one for the offer information. Required when using FIX TagValue encoding (ISO 3531-1). Set to Q=Auction clearing information to provide auction information. Set to J=Empty book to remove bid and offer information. Use for Volume Weighted Auction Price. Use for Currency. Use for Auction Volume. Use for Trading System Phase ODAU. Equivalent to MMT Level 2 - Trading Mode - On Demand Auction (Frequent Batch Auction). Required when using FIX TagValue encoding (ISO 3531-1). Use for Price. Use for both Price Currency (Price Notation is MONE) and Notional Currency (Price Notation is PERC, YIEL or BAPO). Use for Quantity (all) and Notional Amount (only for bonds). Use for Number of Transactions. Use for Quantity (only for bonds when traded in units). Use for Notional Amount (only for ETCs and ETNs) Use for Suspicious Data Flag. Single instance (new, amended or cancelled trade). Required when using FIX TagValue encoding (ISO 3531-1). Use for Price. Use for both Price Currency (Price Notation is MONE) and Notional Currency (Price Notation is PERC, YIEL or BAPO). Use for Notional Amount. Conditionally required unless volume omission flag OMIS is set. Use for Number of Transactions. Single instance (new, amended or cancelled trade). Required when using FIX TagValue encoding (ISO 3531-1). Use for Price. Use for both Price Currency (Price Notation is MONE) and Notional Currency (Price Notation is PERC, YIEL or BAPO). Use for Notional Amount. Conditionally required unless volume omission flag OMIS is set. Use for Number of Transactions. Use for Suspicious Data Flag. Single instance (new, amended or cancelled trade). Required when using FIX TagValue encoding (ISO 3531-1). Use for Price. Use for Price Currency. Use for Quantity. Required when using FIX TagValue encoding (ISO 3531-1). Use for Price. Use for Price Currency. Use for Quantity. Use for Suspicious Data Flag. Single instance (new, amended or cancelled trade). Required when using FIX TagValue encoding (ISO 3531-1). Use for Venue of Execution. Use for both Price Currency (Price Notation is MONE) and Notional Currency (Price Notation is PERC, YIEL or BAPO). Use for Notional Amount. Conditionally required unless volume omission flag VOLO is set. Single instance (new, amended or cancelled trade). Required when using FIX TagValue encoding (ISO 3531-1). Use for Venue of Execution. Use for both Price Currency (Price Notation is MONE) and Notional Currency (Price Notation is PERC, YIEL or BAPO). Use for Notional Amount. Conditionally required unless volume omission flag VOLO is set. Use for Data Quality Indicator Flag. Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). Required when using FIX TagValue encoding (ISO 3531-1). MsgType = W Required when using FIX TagValue encoding (ISO 3531-1). Use for MRMTL. Use for pre-trade core market data (input and output). MsgType = W Required when using FIX TagValue encoding (ISO 3531-1). Use for continuous trading to distinguish aggregated from non-aggregated orderbooks. Use for pre-trade core market data (input and output). MsgType = W Required when using FIX TagValue encoding (ISO 3531-1). Use for MRMTL. Use for pre-trade core market data (input and output). MsgType = W Required when using FIX TagValue encoding (ISO 3531-1). Use for MRMTL. Use for pre-trade core market data (input and output). MsgType = X Required when using FIX TagValue encoding (ISO 3531-1). Use for post-trade core market data (input and output). MsgType = X Required when using FIX TagValue encoding (ISO 3531-1). Use for post-trade core market data (input and output). MsgType = X Required when using FIX TagValue encoding (ISO 3531-1). Use for post-trade core market data (input and output). MsgType = X Required when using FIX TagValue encoding (ISO 3531-1). Use for post-trade core market data (input and output). MsgType = X Required when using FIX TagValue encoding (ISO 3531-1). Use for post-trade core market data (input and output). MsgType = X Required when using FIX TagValue encoding (ISO 3531-1). Use for post-trade core market data (input and output). MsgType = X Required when using FIX TagValue encoding (ISO 3531-1). Use for post-trade core market data (input and output). MsgType = f (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Unique message identifier. Conditionally required when supporting SecurityStatusAck(35=ER) as response message. Use for MRMTL indicator. Field absence indicates that the given market is not the most relevant market in terms of liquidity. Use for Instrument Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (instrument status). MsgType = f (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Use for Instrument Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (instrument status). MsgType = f (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Use for MRMTL indicator. Field absence indicates that the given market is not the most relevant market in terms of liquidity. Use for Instrument Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (instrument status). MsgType = f (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Unique message identifier. Conditionally required when supporting SecurityStatusAck(35=ER) as response message. Use for Instrument Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (instrument status). MsgType = f (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Unique message identifier. Conditionally required when supporting SecurityStatusAck(35=ER) as response message. Use for Instrument Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (instrument status). MsgType = h (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Unique identifier for this message. Conditionally required when supporting TradingSessionStatusAck(35=ES) as response message. Use for System Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (trading system status). MsgType = h (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Unique identifier for this message. Conditionally required when supporting TradingSessionStatusAck(35=ES) as response message. Use for System Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (trading system status). MsgType = h (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Use for System Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (trading system status). MsgType = h (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Unique identifier for this message. Conditionally required when supporting TradingSessionStatusAck(35=ES) as response message. Use for System Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (trading system status). MsgType = h (lowercase) Required when using FIX TagValue encoding (ISO 3531-1). Use for System Status Start Date and Time. Required when using FIX TagValue encoding (ISO 3531-1). Use for regulatory data (trading system status). MsgType = EQ Reference identifier to market data message being acknowledged. Conditionally required when ReportStatus(3113)=3 (Accepted with errors) to provide error details. May be used when ReportStatus(3113)=2 (Rejected) to provide further details beyond RejectText(1328). Conditionally required when ReportStatus(3113)=2 (Rejected). This message may be used as a response to the MarketDataSnapshotFullRefresh(35=W) and MarketDataIncrementalRefresh(35=X) messages. MsgType = ER Required when using FIX TagValue encoding (ISO 3531-1). Conditionally required when ReportStatus(3113)=2 (Rejected). Required when using FIX TagValue encoding (ISO 3531-1). This message may be used as a response to the SecurityStatus(35=f) message. MsgType = ES Required when using FIX TagValue encoding (ISO 3531-1). Conditionally required when ReportStatus(3113)=2 (Rejected). This message may be used as a response to the TradingSessionStatus(35=h) message.