Messages
Type | Name | ID | Category | Description | Pedigree |
|---|---|---|---|---|---|
| 0 | Heartbeat | 1 | Session | The Heartbeat monitors the status of the communication link and identifies when the last of a string of messages was not received. | Added FIX.2.7 |
| 1 | TestRequest | 2 | Session | The test request message forces a heartbeat from the opposing application. | Added FIX.2.7 |
| 2 | ResendRequest | 3 | Session | 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. | Added FIX.2.7 |
| 3 | Reject | 4 | Session | The reject message should be issued when a message is received but cannot be properly processed due to a session-level rule violation. | Added FIX.2.7 |
| 4 | SequenceReset | 5 | Session | The Sequence Reset message has two modes: Gap Fill mode and Reset mode. | Added FIX.2.7 |
| 5 | Logout | 6 | Session | The logout message initiates or confirms the termination of a FIX session. | Added FIX.2.7 |
| 6 | IOI | 7 | Indication | Indication of interest messages are used to market merchandise which the broker is buying or selling in either a proprietary or agency capacity. | Added FIX.2.7 |
| 7 | Advertisement | 8 | Indication | Advertisement messages are used to announce completed transactions. | Added FIX.2.7 |
| 8 | ExecutionReport | 9 | SingleGeneralOrderHandling | 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 | Added FIX.2.7 |
| 9 | OrderCancelReject | 10 | SingleGeneralOrderHandling | 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. | Added FIX.2.7 |
| A | Logon | 11 | Session | The logon message authenticates a user establishing a connection to a remote system. | Added FIX.2.7 |
| B | News | 12 | EventCommunication | The news message is a general free format message between the broker and institution. | Added FIX.2.7 |
| C | 13 | EventCommunication | The email message is similar to the format and purpose of the News message, however, it is intended for private use between two parties. | Added FIX.2.7 | |
| D | NewOrderSingle | 14 | SingleGeneralOrderHandling | The new order message type is used by institutions wishing to electronically submit securities and forex orders to a broker for execution. | Added FIX.2.7 |
| E | NewOrderList | 15 | ProgramTrading | The NewOrderList Message can be used in one of two ways depending on which market conventions are being followed. | Added FIX.2.7 |
| F | OrderCancelRequest | 16 | SingleGeneralOrderHandling | The order cancel request message requests the cancellation of all the remaining quantity of an existing order. | Added FIX.2.7 |
| G | OrderCancelReplaceRequest | 17 | SingleGeneralOrderHandling | The order cancel/replace request is used to change the parameters of an existing order. | Added FIX.2.7 |
| H | OrderStatusRequest | 18 | SingleGeneralOrderHandling | The order status request message is used by the institution to generate an order status message back from the broker. | Added FIX.2.7 |
| J | AllocationInstruction | 19 | Allocation | The Allocation Instruction 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 and is now performed by the new (to version 4.4) Allocation Report and Confirmation messages.,The Allocation Report message should be used for the Sell-side Initiated Allocation role as defined in previous versions of the protocol. | Added FIX.2.7 |
| K | ListCancelRequest | 20 | ProgramTrading | The List Cancel Request message type is used by institutions wishing to cancel previously submitted lists either before or during execution. | Added FIX.2.7 |
| L | ListExecute | 21 | ProgramTrading | 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. | Added FIX.2.7 |
| M | ListStatusRequest | 22 | ProgramTrading | The list status request message type is used by institutions to instruct the broker to generate status messages for a list. | Added FIX.2.7 |
| N | ListStatus | 23 | ProgramTrading | 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. | Added FIX.2.7 |
| P | AllocationInstructionAck | 24 | Allocation | 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. | Added FIX.2.7 |
| Q | DontKnowTrade | 25 | SingleGeneralOrderHandling | 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. | Added FIX.4.0 |
| R | QuoteRequest | 26 | QuotationNegotiation | 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 a Request For Quote (RFQ) | Added FIX.4.0 |
| S | Quote | 27 | QuotationNegotiation | 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. | Added FIX.4.0 |
| T | SettlementInstructions | 28 | SettlementInstruction | 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. | Added FIX.4.1 |
| V | MarketDataRequest | 29 | MarketData | Some systems allow the transmission of real-time quote, order, trade, trade volume, open interest, and/or other price information on a subscription basis. A Market Data Request is a general request for market data on specific securities or forex quotes. | Added FIX.4.2 |
| W | MarketDataSnapshotFullRefresh | 30 | MarketData | The Market Data messages are used as the response to a Market Data Request message. | Added FIX.4.2 |
| X | MarketDataIncrementalRefresh | 31 | MarketData | The second Market Data message format is used for incremental updates. | Added FIX.4.2 |
| Y | MarketDataRequestReject | 32 | MarketData | The Market Data Request Reject is used when the broker cannot honor the Market Data Request, due to business or technical reasons. | Added FIX.4.2 |
| Z | QuoteCancel | 33 | QuotationNegotiation | The Quote Cancel message is used by an originator of quotes to cancel quotes. | Added FIX.4.2 |
| a | QuoteStatusRequest | 34 | QuotationNegotiation | The quote status request message is used for the following purposes in markets that employ tradeable or restricted tradeable quotes: | Added FIX.4.2 |
| b | MassQuoteAcknowledgement | 35 | QuotationNegotiation | Mass Quote Acknowledgement is used as the application level response to a Mass Quote message. | Added FIX.4.2 |
| c | SecurityDefinitionRequest | 36 | SecurityAndTradingSessionDefinitionOrStatus | The Security Definition Request 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. | Added FIX.4.2 |
| d | SecurityDefinition | 37 | SecurityAndTradingSessionDefinitionOrStatus | The Security Definition message is used for the following: 1. Accept the security defined in a Security Definition message. 2. Accept the security defined in a Security Definition message with changes to the definition and/or identity of the security. 3. Reject the security requested in a Security Definition message | Added FIX.4.2 |
| e | SecurityStatusRequest | 38 | SecurityAndTradingSessionDefinitionOrStatus | The Security Status Request message provides for the ability to request the status of a security. | Added FIX.4.2 |
| f | SecurityStatus | 39 | SecurityAndTradingSessionDefinitionOrStatus | The Security Status message provides for the ability to report changes in status to a security. | Added FIX.4.2 |
| g | TradingSessionStatusRequest | 40 | SecurityAndTradingSessionDefinitionOrStatus | The Trading Session Status Request is used to request information on the status of a market. | Added FIX.4.2 |
| h | TradingSessionStatus | 41 | SecurityAndTradingSessionDefinitionOrStatus | The Trading Session Status provides information on the status of a market. | Added FIX.4.2 |
| i | MassQuote | 42 | QuotationNegotiation | The Mass Quote message can contain quotes for multiple securities to support applications that allow for the mass quoting of an option series. | Added FIX.4.2 |
| j | BusinessMessageReject | 43 | Common | Added FIX.4.2 | |
| k | BidRequest | 44 | ProgramTrading | The BidRequest Message can be used in one of two ways depending on which market conventions are being followed. | Added FIX.4.2 |
| l | BidResponse | 45 | SingleGeneralOrderHandling | 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. | Added FIX.4.2 |
| m | ListStrikePrice | 46 | ProgramTrading | 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. | Added FIX.4.2 |
| n | XMLnonFIX | 47 | Session | Added FIX.4.3 | |
| o | RegistrationInstructions | 48 | RegistrationInstruction | 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. | Added FIX.4.3 |
| p | RegistrationInstructionsResponse | 49 | RegistrationInstruction | 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. | Added FIX.4.3 |
| q | OrderMassCancelRequest | 50 | SingleGeneralOrderHandling | The order mass cancel request message requests the cancellation of all 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). | Added FIX.4.3 |
| r | OrderMassCancelReport | 51 | SingleGeneralOrderHandling | 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. | Added FIX.4.3 |
| s | NewOrderCross | 52 | CrossOrders | Used to submit a cross order into a market. The cross order contains two order sides (a buy and a sell). | Added FIX.4.3 |
| t | CrossOrderCancelReplaceRequest | 53 | CrossOrders | Used to modify a cross order previously submitted using the New Order - Cross message. See Order Cancel Replace Request for details concerning message usage. | Added FIX.4.3 |
| u | CrossOrderCancelRequest | 54 | CrossOrders | Used to fully cancel the remaining open quantity of a cross order. | Added FIX.4.3 |
| v | SecurityTypeRequest | 55 | SecurityAndTradingSessionDefinitionOrStatus | The Security Type Request message is used to return a list of security types available from a counterparty or market. | Added FIX.4.3 |
| w | SecurityTypes | 56 | SecurityAndTradingSessionDefinitionOrStatus | The Security Type message is used to return a list of security types available from a counterparty or market. | Added FIX.4.3 |
| x | SecurityListRequest | 57 | SecurityAndTradingSessionDefinitionOrStatus | The Security List Request message is used to return a list of securities from the counterparty that match criteria provided on the request | Added FIX.4.3 |
| y | SecurityList | 58 | SecurityAndTradingSessionDefinitionOrStatus | The Security List message is used to return a list of securities that matches the criteria specified in a Security List Request. | Added FIX.4.3 |
| z | DerivativeSecurityListRequest | 59 | SecurityAndTradingSessionDefinitionOrStatus | The Derivative Security List Request message is used to return a list of securities from the counterparty that match criteria provided on the request | Added FIX.4.3 |
| AA | DerivativeSecurityList | 60 | SecurityAndTradingSessionDefinitionOrStatus | The Derivative Security List message is used to return a list of securities that matches the criteria specified in a Derivative Security List Request. | Added FIX.4.3 |
| AB | NewOrderMultileg | 61 | MultilegOrders | The New Order - Multileg is provided to submit orders for securities that are made up of multiple securities, known as legs. | Added FIX.4.3 |
| AC | MultilegOrderCancelReplace | 62 | MultilegOrders | Used to modify a multileg order previously submitted using the New Order - Multileg message. See Order Cancel Replace Request for details concerning message usage. | Added FIX.4.3 |
| AD | TradeCaptureReportRequest | 63 | TradeCapture | Trade Capture Reporting allows sell-side firms (broker, exchange, ECN) to provide timely reporting of completed trades to an external entity not involved in the execution of the trade. | Added FIX.4.3 |
| AE | TradeCaptureReport | 64 | TradeCapture | The Trade Capture Report 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. • Can be used to report unmatched and matched trades. | Added FIX.4.3 |
| AF | OrderMassStatusRequest | 65 | SingleGeneralOrderHandling | The order mass status request message requests the status for orders matching criteria specified within the request. | Added FIX.4.3 |
| AG | QuoteRequestReject | 66 | QuotationNegotiation | The Quote Request Reject message is used to reject Quote Request messages for all quoting models. | Added FIX.4.3 |
| AH | RFQRequest | 67 | QuotationNegotiation | In tradeable and restricted tradeable quoting markets – Quote Requests are issued by counterparties interested in ascertaining the market for an instrument. | Added FIX.4.3 |
| AI | QuoteStatusReport | 68 | QuotationNegotiation | 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) | Added FIX.4.3 |
| AJ | QuoteResponse | 69 | QuotationNegotiation | The Quote Response message is used to respond to an IOI message or Quote message. | Added FIX.4.4 |
| AK | Confirmation | 70 | 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. This message is also used to report back, confirm or exception, the booking status of each allocation instance. When the buy-side, in response, "affirms" with the ConfirmationAck message, the trade is ready to settle. | Added FIX.4.4 |
| AL | PositionMaintenanceRequest | 71 | PositionMaintenance | Position Maintenance Request | Added FIX.4.4 |
| AM | PositionMaintenanceReport | 72 | PositionMaintenance | Position Maintenance Report | Added FIX.4.4 |
| AN | RequestForPositions | 73 | PositionMaintenance | Request For Positions | Added FIX.4.4 |
| AO | RequestForPositionsAck | 74 | PositionMaintenance | Request for Positions Ack | Added FIX.4.4 |
| AP | PositionReport | 75 | PositionMaintenance | Position Report | Added FIX.4.4 |
| AQ | TradeCaptureReportRequestAck | 76 | TradeCapture | 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 • The Trade Capture Request was invalid for some business reason, such as request is not authorized, invalid or unknown instrument, party, trading session, etc. | Added FIX.4.4 |
| AR | TradeCaptureReportAck | 77 | TradeCapture | 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 | Added FIX.4.4 |
| AS | AllocationReport | 78 | Allocation | Sent from sell-side to buy-side, sell-side to 3rd-party or 3rd-party to buy-side, the Allocation Report (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. In versions of FIX prior to version 4.4, this functionality was provided through the Allocation message. Depending on the needs of the market and the timing of "confirmed" status, the role of Allocation Report can be taken over in whole or in part by the Confirmation message. Note the response to the Allocation Report message is the Allocation Report Ack message. In versions of FIX prior to version 4.4, the Allocation ACK served this purpose. | Added FIX.4.4 |
| AT | AllocationReportAck | 79 | Allocation | The Allocation Report Ack message is used to acknowledge the receipt of and provide status for an Allocation Report message. | Added FIX.4.4 |
| AU | ConfirmationAck | 80 | Confirmation | The Confirmation Ack (aka Affirmation) message is used to respond to a Confirmation message. | Added FIX.4.4 |
| AV | SettlementInstructionRequest | 81 | SettlementInstruction | Added FIX.4.4 | |
| AW | AssignmentReport | 82 | PositionMaintenance | Assignment Reports are sent from a clearing house to counterparties, such as a clearing firm as a result of the assignment process. | Added FIX.4.4 |
| AX | CollateralRequest | 83 | CollateralManagement | 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. | Added FIX.4.4 |
| AY | CollateralAssignment | 84 | CollateralManagement | Used to assign collateral to cover a trading position. This message can be sent unsolicited or in reply to a Collateral Request message. | Added FIX.4.4 |
| AZ | CollateralResponse | 85 | CollateralManagement | Used to respond to a Collateral Assignment message | Added FIX.4.4 |
| BA | CollateralReport | 86 | CollateralManagement | Used to report collateral status when responding to a Collateral Inquiry message. | Added FIX.4.4 |
| BB | CollateralInquiry | 87 | CollateralManagement | Used to inquire for collateral status | Added FIX.4.4 |
| BC | NetworkCounterpartySystemStatusRequest | 88 | Common | Added FIX.4.4 | |
| BD | NetworkCounterpartySystemStatusResponse | 89 | Common | Added FIX.4.4 | |
| BE | UserRequest | 90 | Common | Added FIX.4.4 | |
| BF | UserResponse | 91 | Common | Added FIX.4.4 | |
| BG | CollateralInquiryAck | 92 | CollateralManagement | Used to respond to a Collateral Inquiry | Added FIX.4.4 |
| BH | ConfirmationRequest | 93 | Confirmation | The Confirmation Request message is used to request a Confirmation message. | Added FIX.4.4 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy