Creating a TT FIX Drop Copy session
FIX client drop copy applications connect to TT FIX services through a FIX Drop Copy session.
Use the FIX sessions window to add FIX sessions to your company and configure them for third-party
FIX client access.
To add and configure a FIX Drop Copy session:
- Click More | FIX Sessions in the left navigation pane.
-
At the top of the FIX Sessions window, click +New Session.
- For FIX Type, select FIX Drop Copy.
- Configure the following settings:
- FIX Session Name — Sets the display name of the FIX server.
-
Remote Comp Id — Sets the FIX client ID. This FIX client ID value is sent in
FIX Tag 49 (SenderCompID) by a FIX client connecting to the FIX server. The ID is populated in FIX
Tag 56 (TargetCompID) for all messages sent by the FIX Server to the FIX client. -
Target Sub Id — Sets the receiver ID. This value is sent in FIX Tag 57
(TargetSubId) of the FIX client Logon (A) message.
Notes:If a value is specified for this setting:
- The combination of the Remote Comp Id and Target Sub Id
settings must be unique among all FIX sessions. - The FIX client connecting to this FIX session must supply the same value in tag 57.
Also, if FIX clients send Tag 57, which is optional, in the Logon (A) message, the value must be
supplied in this setting. - The combination of the Remote Comp Id and Target Sub Id
-
Session Password — The password associated with this FIX session and used to
authenticate FIX Servers. FIX Session passwords do not expire and are not subject to any TT account
password restrictions. It must be passed in Tag 96 (RawData) in the Logon (A) message. -
Notification email — Sets the email address company administrators can use to
receive notifications from TT for emergency maintenance, operational or product release information
that could impact the FIX session. -
Country — The country in which the FIX server machine is located.
Based on the country selected, you may also need to provide a State/Province and Zip Code.
-
Send Staged / Synthetic Child order / fill messages — Sets whether to send
order and fill messages to the FIX client for child order of staged or synthetic parent orders. -
Send and receive Order ID values in short form — Sets whether to send
shortened order IDs in tag 37 (OrderId) in order routing and execution report messages. -
Compliance Feed — When enabled, the Drop Copy session will deliver New Order
Single (D), Cancel/Replace (G), New Order Multileg (AB), Multileg Cancel/Replace (AC) and Cancel (F)
messages, plus the related Pending Request (150 = A, E or 6) Execution Report (8) messages. These
compliance messages include high precision timestamps suitable for MIFID II reporting as to when
TT’s order routing software received the request and when it sent the request to the exchange. -
Force sending of Head fills before Leg fills — Sets whether to always send
Head fills (442=3) before sending the individual leg fills (442=2). This setting is supported only
for FIX 4.4 sessions. -
Send FillsGrp as Individual Execution Reports — Sets whether to send an
individual Execution Report (8) message for each entry in the FillsGrp and LegFillsGrp repeating
groups instead of in a group in a single Execution Report (8) message. -
Send TT Internal Account ID and User ID on Execution Reports And Cancel Reject
Messages — Sets whether to send the TT internal IDs for tag 1 (Account) and tag
129 (DeliverToSubId) in tags 18101 (AccountID) and 18102 (UserID), respectively, for Execution
Report (8) and Order Cancel/Replace Request (9) messages. -
Filter AOTC Executions & Add Compliance Messages for AOTC-triggered actions at the
Exchange — Sets whether to filter Avoid Orders That Cross (AOTC) and Compliance
messages. When enabled, FIX Drop Copy will:- Generate compliance messages for AOTC fills / changes that occur against orders resting at
the exchange. - Simultaneously drop any internal fill messages for that action.
- Drop the internal transfer fills/cancels for the aggressing order.
- Generate compliance messages for AOTC fills / changes that occur against orders resting at
-
Send Exchange Fill Updates as Trade Correction Execution Reports — Sets
whether to send exchange fill updates as Execution Report (8) messages instead of Trade Capture
Report (AE) messages for the following markets:- HKEX
- OSE
- SGX
- TOCOM
- NDAQ_EU
- NFI
-
(Session Reset): — Schedule for resetting the FIX Server connection.
To set the reset time:
- Click a day to enable the Reset Time (UTC) fields.
- Set the desired session reset time in UTC time.
-
In the Status section, choose whether to make the session active. The session is inactive
by default. -
In the Account Settings section, enable the Assign All Accounts setting to ensure
that all available accounts for the entire company are assigned to the FIX Drop Copy
session. This includes accounts shared with your company. Dynamically, new accounts will be assigned to the
session as they’re available and deleted accounts will be removed. When this checkbox is unchecked, each
account has to be mapped individually to the FIX Drop Copy session. This setting is enabled by default. - Click +Add in the Company Relationships section to share FIX
sessions with other companies (e.g., to brokers).This allows the FIX Session to be configured for
trading (assigned accounts, connections, etc.) by the shared company. - Click Save Changes.
-
Configure the connection
to the FIX session via TCP or Secured TCP (SSL).
FIX Session management
TT FIX Drop Copy client applications require a FIX session to be created in Setup in order to connect to TT FIX servers. Client applications should be designed with the following session management considerations in mind:
FIX session reset schedules
TT FIX Order Routing sessions are persistent by default and reset on Saturdays
at 22:00 UTC.
Clients may optionally define a custom daily reset time when configuring a FIX
Order Routing session in Setup Setup.
Note: If a FIX client remains connected
to a FIX session when either the default or custom scheduled reset time
occurs, TT’s FIX engine will send a Logout message.
On-demand sequence number resets
By default, message sequence numbers for FIX sessions are reset when TT resets all FIX sessions. Message sequence numbers can also be reset, when desired, by setting Tag 34 (MsgSeqNum) = 1 and Tag 141 (ResetSeqNumFlag) = Y when sending a Logon (A) message.
ClOrdID uniqueness
TT FIX will ensure ClOrdID (tag 11) uniqueness for:
- All orders entered since the last session reset (Saturday @ 22:00 UTC by default or per custom schedule in Setup)
- All GTC / GTDate orders entered in previous sessions that were still working at the start of the current sesssion.
For more information, refer to the ClOrdID tag description in the New Order Single (D) message.
Handling connection problems
If your FIX client application disconnects and subsequently reconnects, TT’s
FIX engine will perform an internal recovery process to query our cloud based
order book database and will deliver all unsent execution reports by applying
an incremental sequence number that picks up where we left off prior to the
disconnect. The session recovery process can be considered complete in all
cases with a News message [35=B].
This eliminates the requirement for your FIX client application to detect a
gap on the session level and request missed execution reports while
disconnected. This also allows FIX client applications to failover seamlessly
into a different datacenter without sequence number consideration.
Handling missed messages
If your FIX client application disconnects and was unable to process
executions prior to the disconnect, TT’s FIX engine supports the standard
message replay mechanism specified by the FIX Protocol by honoring Resend
Request [2] messages received from FIX client applications.
In extreme cases where your FIX client application unexpectedly disconnected
and required intervention on your side to reset sequence numbers that resulted
in a subsequent Logon with 141=Y and 34=1, TT’s FIX engine will still perform
a session recovery process that will query our cloud based order book database
for executions marked as undelivered and apply an incremental sequence number
to each message message. In this case, Logon [34=1], missed executions [34=2,
3, etc]. The session recovery process can be considered complete in all cases
with a News message [35=B].
In the scenario where although TT delivered all relevant execution reports to
your FIX client application, your internal system may have experienced an
issue and was unable to process the messaging. TT’s FIX Engine is aware of
sent messages, but we are unaware of your application’s success or failure to
process them. If your FIX client application also required a sequence number
reset and cannot request a Resend Request [2] message, executions can be
retrieved through our REST API [link to REST].
TT FIX Drop Copy overview
The drop copy configuration type allows FIX clients to use all functionality offered by the TT FIX Adapter except for
routing orders. Consequently, FIX clients can connect to a drop copy TT FIX Adapter to listen for order
acknowledgments and fills.
Getting Started
To begin creating an order routing client application using TT FIX, you will need to:
- Download the TT FIX 4.2
and 4.4 schemas. This schema summarizes the supported FIX messages and tags. - Create
a FIX Drop Copy Session in Setup. The FIX session is used by the client application to connect to the TT
FIX Drop Copy service. - Configure
client connectivity. Create and configure client connection to TT FIX Order Routing services via the
Internet or Stunnel.
FIX Compliance Feed
TT FIX Drop Copy includes a “Compliance Feed” option that enables customers to receive a full Order Audit Trail in
FIX format for all FIX, screen and algo order flow occurring in the TT system.
When enabled, the Drop Copy server will synthesize in real-time the appropriate new order, cancel/replace, cancel and
pending messages, including timestamps for each message accurate to the MIFID II RTS 25 standard, for all executions
received on the customer’s Drop Copy feed.
- For synthetic New Order Single (D), Order Cancel-Replace (G), New Order Multileg (AB), Multileg Order
Cancel-Replace (AC) and Order Cancel Request (F) messages, TransactionTime (FIX Tag 60) represents the time that
the message was sent to the TT Order Connector from a TT trading application. This includes TT Web, TT Desktop,
TT FIX, Algo Server, etc. - For synthetic pending Execution Report (8) messages, ExecType (FIX Tag 150 = A, E or 6), TransactionTime (FIX
Tag 60) represents the time that the request message was sent from the TT Order Connector to the execution
venue.
TT FIX schema
System overview
The TT FIX service allows customers to receive real-time copies of all of their orders submitted through the TT platform, along with their corresponding fills. To use this service, customers must develop FIX clients capable of connecting to and communicating with the TT FIX.
TT FIX supports a subset of the FIX protocol (Version 4.2 with Errata 20010501 and Version 4.4) message types and tags within its message types. Refer to the website http://www.fixtradingcommunity.org/ for additional FIX tag descriptions and message definitions. Both production and UAT versions of the TT FIX schema are available for download at the following link:
https://library.tradingtechnologies.com/tt-fix/general/System_Overview.html#fix-schemas
The second line of each TT FIX schema file contains an XML comment that identifies the schema’s publication date and internal version information, similar to the following.
<!-- TT FIX Version: UAT 2025-08-01 Git:16bc4b86e3c94bef40c3dc55c5314c16df9c9930 MD5:998190c7d44e5636f42569d1279400ee -->
Note: TT FIX supports only those messages and tags described in this document. Do not submit other messages or tags to TT FIX, as doing so can produce unexpected results.