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 is used by the sending application to reset the incoming sequence number on the opposing side. | 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 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. Reject orders 6. 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 to the News message, however, it is intended for private use between two parties. | Added FIX.2.7 | |
| D | OrderSingle | 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 | OrderList | 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 | Allocation | 19 | Allocation | The Allocation message provides the ability to specify how an order or set of orders should be subdivided amongst one or more accounts. | 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. | 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. | Added FIX.2.7 |
| P | AllocationAck | 24 | Allocation | The allocation ACK message is used to acknowledge the receipt and status of an allocation message received from the institution. | Added FIX.2.7 Updated EP282 |
| Q | DontKnowTrade | 25 | SingleGeneralOrderHandling | The Don’t Know Trade (DK) message notifies a trading partner that an electronically received execution has been rejected. | 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. | Added FIX.4.0 |
| S | Quote | 27 | QuotationNegotiation | The quote message is used as the response to a Quote Request message and can be used to publish unsolicited quotes. | Added FIX.4.0 |
| T | SettlementInstructions | 28 | SettlementInstruction | The Settlement Instructions message provides either the broker’s or the institution’s instructions for trade settlement. | Added FIX.4.1 |
| V | MarketDataRequest | 29 | MarketData | Some systems allow the transmission of real-time quote, order, trade and/or other price information on a subscription basis. | 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 by the institution to generate an execution report that contains the quote status message back from the counterparty. | Added FIX.4.2 |
| b | QuoteAcknowledgement | 35 | QuotationNegotiation | An optional response to Quote, Mass Quote, Quote Cancel, and Quote Request message is the Quote Acknowledgement 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 complex security made up of one or more underlying securities. 2. Request a list of the Security Types that can be traded with the second party. 3. Request a list of Securities that can be traded with the second party. This request can optionally be qualified with Symbol, TradingSessionID, SecurityExchange, and Security Type. | 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 4. Return a list of Security Types 5. Return a list of Securities | 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 | 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 | The Business Message Reject message can reject an application-level message which fulfills session-level rules and cannot be rejected via any other means. | 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 | ProgramTrading | 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 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy