Drop Copy message flows
A FIX client starts a FIX Drop Copy session by sending a Logon (A) message to TT FIX and ends the session by calling the Logout (5) message. While connected to a FIX Drop Copy session, a FIX client engages in a series of message conversations (requests and responses) with TT FIX to receive order and fills. Typically, market data message conversations involve the following request and response messages.
| Inbound | Outbound |
|---|---|
| Execution Report (8) The following messages are sent only when the Drop Copy session enables its Compliance Feed setting. | Heartbeat (0) |
Common message flows
- The drop copy message flow begins with TT FIX sending the FIX client the following order and fill messages:
- Execution Report (8)
- Order Cancel Reject (9)
- Trade Capture Report (AE)
(1A) If the Compliance Feed is enabled for the Drop Copy session in Setup, TT FIX also sends copies of order-routing requests.
(1B) If the FIX client receives a Trade Capture Report (AE) message, it can optionally send a Trade Capture Report Ack (AR) message.
- Because the primary purpose of a Drop Copy session is to listen for messages, it does not following the typical request/response paradigm. A FIX Drop Copy client needs to send a Heartbeat (0) message every 30 seconds to maintain its connection.
- At any time, a FIX client can send an Order Status Request (H) message to request the status of an existing order.
- TT FIX sends an Execution Report (8) message in response to the Order Status Request (H) message.