Application Messages By Name

Name Description
Advertisement (7)

Advertisement (7) messages are used to announce completed transactions. The Advertisement (7) 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 (3) .

Allocation Instruction (J)

The Allocation Instruction (J) message provides the ability to specify how an order or set of orders should be subdivided amongst one or more accounts. In versions of FIX prior to version 4.4, this same message was known as the Allocation message. Note in versions of FIX prior to version 4.4, the allocation message was also used to communicate fee and expense details from the Sellside to the Buyside. This role has now been removed from the Allocation Instruction (J) and is now performed by the new (to version 4.4) Allocation Report (AS) and Confirmation (AK) messages.,The Allocation Report (AS) message should be used for the Sell-side Initiated Allocation role as defined in previous versions of the protocol.

Allocation Instruction Ack (P)

In versions of FIX prior to version 4.4, this message was known as the Allocation ACK message.

Allocation Report (AS)

Sent from sell-side to buy-side, sell-side to 3rd-party or 3rd-party to buy-side, the Allocation Report (Claim) (AS) 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. In versions of FIX prior to version 4.4, this functionality was provided through the Allocation Instruction (J) message. Depending on the needs of the market and the timing of "confirmed" status, the role of Allocation Report (AS) can be taken over in whole or in part by the Confirmation (AK) message.

Allocation Report Ack (AT)

The Allocation Report Ack (AT) message is used to acknowledge the receipt and status of an Allocation Report (AS) message.

Assignment Report (AW)

Assignment Reports are sent from a clearing house to counterparties, such as a clearing firm as a result of the assignment process Communication Scenarios.

Bid Request (k)

The Bid Request (k) message can be used in one of two ways depending on which market conventions are being followed.

Bid Response (l)

The Bid Response (l) message can be used in one of two ways depending on which market conventions are being followed.

Business Message Reject (j)

The Business Message Reject (j) 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 (3) message should be issued.

Collateral Assignment (AY)

Used to assign collateral to cover a trading position. This message can be sent unsolicited or in reply to a Collateral Request (AX) message.

Collateral Inquiry (BB)

Used to report collateral status when responding to a Collateral Inquiry (BB) message.

Collateral Inquiry Ack (BG)

Used to respond to a Collateral Inquiry (BB) in the following situations:

Collateral Report (BA)

Used to inquire for collateral status.

Collateral Request (AX)

An initiator that requires collateral from a respondent sends a Collateral Request (AX) . 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 (AY) is expected as a response to a request for collateral.

Collateral Response (AZ)

Used to respond to a Collateral Assignment (AY) message.

Confirmation (AK)

The Confirmation (AK) 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.

Confirmation Ack (AU)

The Confirmation Ack (aka Affirmation) (AU) message is used to respond to a Confirmation (AK) message.

Confirmation Request (BH)

The Confirmation Request (BH) message is used to request a Confirmation (AK) message.

Cross Order Cancel Request (u)

Used to fully cancel the remaining open quantity of a cross order.

Cross Order Cancel/Replace Request (t)

Used to modify a cross order previously submitted using the New Order - Cross (s) message. See Order Cancel/Replace Request (G) for details concerning message usage.

Derivative Security List (AA)

The Derivative Security List (AA) message is used to return a list of securities that matches the criteria specified in a Derivative Security List Request (z) .

Derivative Security List Request (z)

The Derivative Security List Request (z) message is used to return a list of securities from the counterparty that match criteria provided on the request

Don't Know Trade (Q)

The Don't Know Trade (DK) (Q) message notifies a trading partner that an electronically received execution has been rejected. This message can be thought of as an execution reject message.

Email (C)

The Email (C) message is similar to the format and purpose of to the News (B) message, however, it is intended for private use between two parties.

Execution Report (8)

The Execution Report (8) 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
Indication of Interest (6)

Indication of interest (6) 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.

List Cancel Request (K)

The List Cancel Request (K) message type is used by institutions wishing to cancel previously submitted lists either before or during execution.

List Execute (L)

The List Execute (L) 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.

List Status (N)

The List Status (N) message is issued as the response to a List Status Request (M) message sent in an unsolicited fashion by the sell-side. It indicates the current state of the orders within the list as they exists at the broker's site. This message may also be used to respond to the List Cancel Request (K) .

List Status Request (M)

The List Status Request (M) message type is used by institutions to instruct the broker to generate status messages for a list.

List Strike Price (m)

The Strike Price (m) message is used to exchange strike price information for principal trades. It can also be used to exchange reference prices for agency trades.

Market Data - Incremental Refresh (X)

The second Market Data message format is used for incremental updates. Market Data Entries may have an MDEntryID (278) unique among all currently active Market Data Entries so they can be referenced for the purposes of deleting and changing them later. When changing a Market Data Entry, it may keep the same MDEntryID (278) , in which case only MDEntryID (278) would be populated, or the MDEntryID (278) may change, in which case MDEntryID (278) will contain the new ID, and MDEntryRefID (280) will contain the ID of the Market Data Entry being changed. An MDEntryID (278) can be reused within a day only if it has first been deleted.

Market Data - Snapshot/Full Refresh (W)

The Market Data messages are used as the response to a Market Data Request (V) message. In all cases, one Market Data message refers only to one Market Data Request (V) . 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, the trade volume or open interest for a security, or any combination of these.

Market Data Request (V)

Some systems allow the transmission of real-time quote, order, trade, trade volume, open interest, and/or other price information on a subscription basis. A Market Data Request (V) is a general request for market data on specific securities or forex quotes.

Market Data Request Reject (Y)

The Market Data Request Reject (Y) is used when the broker cannot honor the Market Data Request (V) , 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.

Mass Quote (i)

The Mass Quote (i) 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).

Mass Quote Acknowledgement (b)

Mass Quote Acknowledgement (b) is used as the application level response to a Mass Quote (i) message. The Mass Quote Acknowledgement (b) contains a field for reporting the reason in the event that the entire quote is rejected ( QuoteRejectReason (300) ). The Mass Quote Acknowledgement (b) also contains a field for each quote that is used in the event that the quote entry is rejected ( QuoteEntryRejectReason (368) ). The ability to reject an individual quote entry is important so that the majority of quotes can be successfully applied to the market instead of having to reject the entire Mass Quote (i) for a minority of rejected quotes.

Multileg Order Cancel/Replace Request (AC)

Used to modify a multileg order previously submitted using the New Order - Multileg (AB) message. See Order Cancel/Replace Request (G) for details concerning message usage.

Network (Counterparty System) Status Request (BC)

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 (935) 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 Network Status Request (BC) message with a NetworkRequestType (935) of StopSubscribing.

Network (Counterparty System) Status Response (BD)

This message is sent in response to a Network (Counterparty System) Status Request (BC) message.

New Order - Cross (s)

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 (548) .

New Order - List (E)

The New Order - List (E) Message can be used in one of two ways depending on which market conventions are being followed.

New Order - Multileg (AB)

The New Order - Multileg (AB) is provided to submit orders for securities that are made up of multiple securities, known as legs.

New Order - Single (D)

The New Order (D) message type is used by institutions wishing to electronically submit securities and forex orders to a broker for execution.

News (B)

The news (B) 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 (B) message can be originated at either the broker or institution side.

Order Cancel Reject (9)

The Order Cancel Reject (9) message is issued by the broker upon receipt of a Cancel Request (F) or Order Cancel/Replace Request (G) message which cannot be honored. Requests to change price or decrease quantity are executed only when an outstanding quantity exists. Filled orders cannot be changed (i.e quantity reduced or price change. However, the broker/sellside may support increasing the order quantity on a currently filled order).

Order Cancel Request (F)

The Order Cancel Request (F) message requests the cancelation of all of the remaining quantity of an existing order. Note that the Order Cancel/Replace Request (G) should be used to partially cancel (reduce) an order.

Order Cancel/Replace Request (G)

The Order Cancel/Replace Request (G) is used to change the parameters of an existing order.

Order Mass Cancel Report (r)

The Order Mass Cancel Report (r) is used to acknowledge an Order Mass Cancel Request (q) . Note that each affected order that is canceled is acknowledged with a separate Execution Report (8) or Order Cancel Reject (9) message.

Order Mass Cancel Request (q)

The Order Mass Cancel Request (q) message requests the cancelation 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).

Order Mass Status Request (AF)

The Order Mass Status Request (AF) message requests the status for orders matching criteria specified within the request.

Order Status Request (H)

The Order Status Request (H) message is used by the institution to generate an order status message back from the broker.

Position Maintenance Report (AM)

Position Maintenance Request (AL)

Position Report (AP)

Quote (S)

The Quote (S) message is used as the response to a Quote Request (R) or a Quote Response (AJ) message in both indicative, tradeable, and restricted tradeable quoting markets.

Quote Cancel (Z)

The Quote Cancel (Z) message is used by an originator of quotes to cancel quotes.

Quote Request (R)

In some markets it is the practice to request quotes from brokers prior to placement of an order. The Quote Request (R) message is used for this purpose. This message is commonly referred to as an Request For Quote (RFQ) (AH) .

Quote Request Reject (AG)

The Quote Request Reject (AG) message is used to reject Quote Request (R) messages for all quoting models.

Quote Response (AJ)

The Quote Response (AJ) message is used to respond to a Indication of Interest (6) message or Quote (S) message. It is also used to counter a Quote or end a negotiation dialog.

Quote Status Report (AI)

The Quote Status Report (AI) message is used:

Quote Status Request (a)

The Quote Status Request (a) 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 (117) to specify the target quote).
  • To subscribe and unsubscribe for Quote Status Report (AI) messages for one or more securities.
RFQ Request (AH)

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 (AH) 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

Registration Instructions (o)

The Registration Instructions (o) 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.

Registration Instructions Response (p)

The Registration Instructions Response (p) message type may be used by broker or fund manager (for CIV) in response to a Registration Instructions (o) message submitted by an institution or retail intermediary for an order or for an allocation.

Request for Positions (AN)

Request for Positions Ack (AO)

Security Definition (d)

The Security Definition (d) message is used for the following:

  1. Accept the security defined in a Security Definition (d) message.
  2. Accept the security defined in a Security Definition (d) message with changes to the definition and/or identity of the security.
  3. Reject the security requested in a Security Definition (d) message
Security Definition Request (c)

The Security Definition Request (c) message is used for the following:

  1. Request a specific Security to be traded with the second party. The request security can be defined as a multileg security made up of one or more instrument legs.
Security List (y)

The Security List (y) message is used to return a list of securities that matches the criteria specified in a Security List Request (x) .

Security List Request (x)

The Security List Request (x) message is used to return a list of securities from the counterparty that match criteria provided on the request

Security Status (f)

The Security Status (f) message provides for the ability to report changes in status to a security. The Security Status (f) message contains fields to indicate trading status, corporate actions, financial status of the company. The Security Status (f) message is used by one trading entity (for instance an exchange) to report changes in the state of a security.

Security Status Request (e)

The Security Status Request (e) message provides for the ability to request the status of a security. One or more Security Status (f) messages are returned as a result of a Security Status Request (e) message.

Security Type Request (v)

The Security Type Request (v) message is used to return a list of security types available from a counterparty or market.

Security Types (w)

The Security Types (w) message is used to return a list of security types available from a counterparty or market.

Settlement Instruction Request (AV)

The Settlement Instruction Request (AV) message is used to request standing settlement instructions from another party. This could be:

  • A buyside firm requesting standing instructions from a sellside firm.
  • A sellside firm requesting standing instructions from a buyside firm.
  • A sellside or buyside firm requesting standing instructions from a third party central static data database.
  • A third party central static data database requesting standing instructions from a sellside or buyside firm.

Settlement Instructions (T)

The Settlement Instructions (T) 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.

Trade Capture Report (AE)

The Trade Capture Report (AE) message can be:

  • Used to report trades between counterparties.
  • Used to report trades to a trade matching system
  • Can be sent unsolicited between counterparties.
  • Sent as a reply to a Trade Capture Report Request (AD) .
  • Can be used to report unmatched and matched trades.
Trade Capture Report Ack (AR)

The Trade Capture Report Ack (AR) message can be:

  • Used to acknowledge trade capture reports received from a counterparty
  • Used to reject a trade capture report received from a counterparty
Trade Capture Report Request (AD)

The Trade Capture Report Request (AD) can be used to:

Trade Capture Report Request Ack (AQ)

The Trade Capture Request Ack (AQ) message is used to:

  • Provide an acknowledgement to a Trade Capture Report Request (AD) in the case where the Trade Capture Report Request (AD) 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 (AD) 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 (AD)
  • The Trade Capture Request was invalid for some business reason, such as request is not authorized, invalid or unknown instrument, party, trading session, etc.

Trading Session Status (h)

The Trading Session Status (h) provides 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.

Trading Session Status Request (g)

The Trading Session Status Request (g) 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.

User Request (BE)

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.

User Response (BF)

This message is used to respond to a User Request (BE) message, it reports the status of the user after the completion of any action requested in the User Request (BE) message.

XML message (n)

The XML message (e.g. non-FIX MsgType) (n) is used to transmitting XML content which is not defined with a FIX MsgType. XML content is enclosed in a traditional "Tag=Value" FIX standard header via the standard header's XmlDataLen and XmlData fields and followed by the "Tag=Value" FIX standard trailer.