Trade
Overview
TT Platform
Description
Task
Browser Access
Description
Task
Videos
TT Desktop
Description
Task
Videos
Reference
Workspace Windows
Description
Task
Videos
Widgets
Description
Task
Preferences
Description
Viewing Market Data
Time and Sales
Task
Reference
Description
Depth
Description
Task
Reference
Market Grid
Description
Task
Videos
Reference
Product Grid
Description
Task
Reference
Spread Matrix
Description
Task
Videos
Reference
Position in Queue (PIQ)
Basic Order Entry
TT Order Types
Description
Task
Videos
Reference
Case Studies
TT Premium Order Types
Description
Task
Reference
Order Ticket
Description
Task
Use Cases
Reference
MD Trader®
Description
Task
Videos
Reference
Order Profiles
Description
Task
Reference
Routing Rules
Description
Task
Blocktrader
Description
Task
Videos
Reference
Trading Crypto on TT
Description
Task
Videos
Reference
Trading on B3
Order Management
Order Book
Description
Task
Reference
Floating Order Book
Description
Task
Reference
Fills
Description
Task
Reference
Positions
Description
Task
Reference
Orders and Fills
Description
Task
Reference
Audit Trail
Description
Task
Reference
Audit Query
Description
Task
Reference
Account List
Description
Task
Videos
Reference
Position Manager
Description
Task
Reference
Alert Manager and Alert Viewer
Description
Task
Videos
Reference
Account & User Restrictions
Description
Task
Reference
Balances
Description
Task
Reference
TT® OMS
Care Orders
Description
Task
Videos
Reference
Lock and Release
Description
Task
Bulking
Description
Task
Videos
Stitching and Splitting
Description
Task
Combining
Description
Task
Order Passing
Description
Task
Use Cases
Order Exceptions
Description
Task
Options
Options Risk
Description
Task
Videos
Reference
QuikStrike
Description
Task
TT Uncovered 3.0
Description
Task
TT Uncovered 2.0
Description
Task
Volatility Calculator
Description
Task
Expiration Manager
Description
Task
Watchlist
Description
Task
Videos
Reference
Options Risk Matrix
Description
Task
Videos
Reference
Options on TT
Description
Videos
Strategy Creation
Description
Task
Use Cases
Reference
Counterparty Manager
Description
Task
RFQ with Counterparties
Description
Task
RFQ Viewer
Description
Task
Videos
Reference
Electronic Eye
Description
Task
Videos
Reference
Vol Curve Manager
Description
Task
Use Cases
Videos
Reference
Options Trade Monitor
Description
Task
Videos
Reference
Options Chain
Description
Task
Use Cases
Videos
Reference
Spread Trading
Autospreader
Description
Task
Use Cases
Videos
Reference
Autospreader Rules
Description
Task
Videos
Reference
Hedge Manager
Description
Task
Videos
Reference
Trading in Yield
Description
Task
Use Cases
Reference
Aggregator
Description
Task
Videos
Reference
Algo Trading
Algo Dashboard
Description
Task
Videos
Reference
Template Manager
Description
Task
Order Management Algos (OMAs)
Autotrader
Description
Task
Reference
Videos
Excel integration with TT
Description
Task
Videos
Reference
Market-Making Algos
Analytics
Charts
Description
Technical Indicators
Task
Videos
Reference
Trader Analytics
Description
Task
Reference
ADL
ADL Overview
Introduction to ADL
Description
Task
Videos
Reference
ADL Basic Concepts
Description
Task
Reference
Building your first algo
Lessons
Advanced concepts
Description
Task
Case Studies
Jump blocks
Group blocks
Virtualized blocks
Library blocks
Trading Blocks
Discrete blocks
Arithmetic blocks
Basic blocks
Logic blocks
Miscellaneous blocks
Setup
Setup Overview
Getting Started
Description
Task
Videos
Reference
Supported Order Types and TIFs
Company Administration
Connections
Description
Task
Videos
Reference
Accounts
Description
Task
Videos
Use Cases
Reference
Users
Description
Task
Videos
Reference
Company
Description
Task
Reference
Order Tag Defaults
Description
Task
Account Administrators
Description
Task
TT Premium Services
Description
Task
TT Access
Description
Task
Advanced Features
Description
Risk Management
Risk Administration
Description
Task
Risk Limits
Description
Task
Videos
Reference
Pre-Trade Portfolio Risk
Description
Task
Reference
Order Cross Prevention
Description
Task
Videos
KRM Limits
Description
Task
TT® OMS
TT OMS Administration
Description
Task
Use Cases
Reference
Exchanges: Americas
FMX
Description
Task
NFI
Task
Nodal
Description
Task
MX
Description
Task
MIAX_FUT_NY
Description
Task
MIAX_FUT_CH
Description
Task
MexDer
Description
Task
ICE
Description
Task
Goldman Sachs Commodity Blocks (GSCB)
Description
Task
Referece
FMX_USTF
Description
Task
B3
Description
Task
Fenics
Description
Task
EBS Market
Description
Task
EBS Direct
Description
Task
Dealerweb
Description
Task
CME
Description
Task
CFE
Description
Task
Cboe FX
Description
Task
Reference
CBOE
Description
Task
Exchanges: EMEA
ICE_L
Description
Task
WSE
Description
Task
Nord Pool
Description
Task
Reference
NASDAQ_NED
Description
Task
NDAQ_EU
Description
Task
MEFF
Description
Task
LSE
Description
Task
LME NTP
Description
Task
LME
Description
Task
JSE
Description
Task
ATHEX
Description
Task
GFO-X
Description
Task
Euronext
Description
Task
Eurex
Description
Task
Videos
Eris
Description
Task
EPEX SPOT
Description
Task
Reference
EEX
Description
Task
DGCX
Description
Task
BIST
Description
Task
Exchanges: Asia/Pacific
ABX
Description
Task
ASX
Description
Task
FEX
Description
Task
HKEx
Description
Task
JPX
Description
Task
NSE
Description
Task
NZX
Description
Task
SGX
Description
Task
SGX GIFT
Description
Task
TAIFEX
Description
Task
TFEX
Description
Task
TFX
Description
Task
CoinFLEX
Task
Exchanges: Crypto
Coinbase
Description
Task
Kraken
Description
Task
FIX Support
FIX Ruleset
Description
Task
FIX Sessions
Description
Task
Secondary Accounts
Description
Task
Monitor
TT Mobile
TT Backtesting
APIs
TT REST API 2.0
Getting Started
API Reference
TT REST API 2.0 (UAT)
Getting Started
API Reference
TT .NET SDK
Getting started with TT .NET SDK
Creating the application framework
Working with instruments
Subscribing for market data
More about prices
An in-depth look at the Price class
Working with orders and fills
Handling trade subscriptions
Working with trade subscriptions
Working with Algos
Algo Server
TT Order Types
TT Premium Order Types
Advanced Concepts and Options
Appendix
TT CORE SDK
Getting Started with TT Core SDK
Creating Application Framework
Working With Instruments
Subscribing for Market Data
Working with Orders and Fills
Creating a TT Application Server
Appendix
TT Trade Surveillance
Overview
Using TT Trade Surveillance
Cluster View
Core Models
Market Abuse Models
Cross Product Models
Spoofing Models
Improperly Matched Trade Models
Market Rate Models
Trading Behaviors Models
Miscellaneous Models
Configurable Models
Reports
Reference
TT FIX Services
TT FIX General
Getting Started
FIX Message Structure
Session messages
TT FIX Order Routing
Overview
TT FIX message conversations
Supported application messages
TT FIX Market Data
Overview
TT FIX message conversations
Supported application messages
TT FIX Drop Copy Out
Overview
TT FIX Message Conversations
Supported application messages
Compliance Feed messages
TT FIX Drop Copy In
Overview
Supported application messages
TT FIX Gateway
Getting Started
FIX Message Structure
Components
Session messages
Price Gateway Messages
Order Gateway Messages
TT FIX Recovery
Overview
FIX Recovery Methods
Supported application messages
Compliance Feed Messages
MiFID II Support

Business Message Reject (j) Message

Business Message Reject (j) Message

Purpose

Used to reject an application-level request that cannot be rejected by other means

Message Direction

From TT FIX to FIX client

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Business Message Reject (j) message is used by the TT FIX whenever it rejects an application-level message that fulfills session-level rules but cannot be rejected via any other means (i.e. Order Cancel Reject (9) message).

For example, suppose a FIX client sends an Order Cancel/Replace Request (G) message where Tag 11 (ClOrdID) matches an existing client order ID. When TT FIX receives the message, it verifies the validity of the message. However, business rules require that a client order ID remains unique for the trading session. Therefore, TT FIX responds with a Business Message Reject (j) message.

Related Information

Any application request message

Market Data Incremental Refresh (X) Message

Market Data Incremental Refresh (X) message

Purpose

Used to send updated market data for an instrument

Message Direction

From TT FIX to FIX client

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Market Data Incremental Refresh (X) message is used to send updates
whenever the market data changes for an instrument to which a FIX client
subscribes for incremental updates.

Calculating entry positions

Market Data Incremental Refresh (X) messages can contain multiple New,
Delete and Change actions for the same contract and MDEntryType. The FIX
client must take into account that Tag 290 (MDEntryPositionNo) in an
update always indicates the position of the entry before processing the
current message.

The following shows an example of an algorithm you can use to process
market depth updates:

  • Create a ladder data structure that is sorted by price.

  • Create a before instance and an after instance.

  • Populate both instances with the
    Market
    Data Snapshot (W)

    message.

  • When a Market Data Incremental Refresh (X) is received and:

    • Tag 279 (MDUpdateAction) is 0 (New), insert it directly into the
      after instance.
    • Tag 279 (MDUpdateAction) is 1 (Change), apply the quantity change
      to the before instance.
    • Tag 279 (MDUpdateAction) is 2 (Delete), mark it for deletion in
      the before instance but do not actually delete it.
  • After the entire Market Data Incremental Refresh (X) is processed in
    this manner, insert all records not marked for deletion in the
    before instance into the after instance.

  • Delete the contents of the before instance.

  • Copy the contents of after instance to the before instance.

  • Display the after instance to the user.

Market Data Request (V) Message

Market Data Request (V) Message

Purpose

Used to request or manage subscriptions for market data

Message Direction

From FIX client to TT FIX

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Market Data Request (V) message is used by a FIX client to request
market data information from TT FIX. You can request information like the
top of book (Bid, Ask, and session prices) and market depth data.

TT FIX responds to a Market Data Request (V) message with a
Market Data Snapshot Full Refresh (W)
message. Additionally:

  • If the FIX Client sets Tag 263 (SubscriptionRequestType) to 0, TT FIX
    sends no further messages. It does not update the market data.

  • If the FIX Client sets Tag 263 (SubscriptionRequestType) to 1, TT FIX
    updates market data according to the setting the FIX Client uses in
    Tag 265 (MDUpdateType):

  • If the FIX Client sets Tag 263 (SubscriptionRequestType) to 2, TT FIX
    stops sending updates.

If TT FIX cannot fulfill a request for market data because the request
contains an invalid instrument, it sends a
Market Data Request Reject (Y)
message.

Note: If you submit this request for an exchange whose
Price Server is down, TT FIX also responds with a
Market Data Request Reject (Y)
message.

Some exchanges disseminate implied prices as well as direct (Bid/Ask)
prices. Trying to merge these two separate price streams can result in
crossed markets for a brief moment. TT FIX forwards all market data
updates from exchanges, so FIX clients can encounter this scenario as
well. FIX clients that subscribe for direct and implied prices should be
written to account for this possibility.

Market Data Request Reject (Y) Message

Market Data Request Reject (Y) Message

Purpose

Used to send the reason for rejecting a market data request

Message Direction

From TT FIX to FIX client

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Market Data Request Reject (Y) message is used by TT FIX when it cannot fulfill a FIX client request for market data.

Related Information

Market Data Request (V)

Market Data Snapshot (W) Message

Market Data Snapshot (W) message

Purpose

Used to return a snapshot of market prices

Message Direction

From TT FIX to FIX client

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Market Data Snapshot Full Refresh (W) message is used by TT FIX to respond to a Market
Data Request (V)
in the following cases:

  • One time, immediately after an incremental subscription before getting the initial incremental updates.
  • Tag 263 (SubscriptionRequestType) in the request is 0, indicating the client wants a single market
    snapshot.
  • Tag 263 (SubscriptionRequestType) in the request is 1 and Tag 265 (MDUpdateType) is 0, indicating the
    client subscribed to full market updates.

Quote Request (R) Message

Quote Request (R) message

Purpose

Used to request quotes from brokers prior to placing an order.

Note: When a FIX client sends a
Market Data Request (V)
for a given instrument with SubscriptionRequestType=1 to
create a market data subscription, that client is automatically subscribed
for RFQ messages for that instrument.

Message Direction

From TT FIX to FIX client only. FIX clients cannot submit Quote Requests
(RFQs) via the TT Security Data service.

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Quote Request (R) message is used to request quotes from brokers prior
to placement of an order. This message is commonly referred to as a
Request For Quote (RFQ).

Security Definition (d) Message

Security Definition (d) Message

Purpose

Used to send contract information in response to a security definition
request

Message Direction

From TT FIX to a FIX client

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Security Definition (d) message is used to send information about an
exchange-listed instrument. TT FIX sends zero or more of these messages to
a FIX client in response to a Security Definition Request (c). A security
definition contains all standing data at the markets that matches the
filter criteria sent in the Security Definition Request (c). After TT FIX
delivers standing data to the FIX client, TT FIX sends unsolicited updates
to that list of standing data (for instance, if a market lists a new
product at midday).

Determining tick sizes and tick values

To determine the tick size and tick value of a given contract, the FIX
client must:

  • In the
    Security Definition Request (c)
    message, set Tag 17000 (RequestTickTable) = Y.
  • With the resulting Security Definition (d) message, calculate the
    values using the following algorithm.

    if tag 16456 (NumTickTblEntries) == 0
    {
      (The tick size (and tick value) are the same for all prices.)
      Tick Size (for all prices) = Tag 16552 (ExchTickSize)
      Tick Value (for all prices) = Tag 16552 (ExchTickSize) * Tag 16554 (ExchPointValue)
    }
    else
    {
      (The tick size and tick value vary by price level.)
      Base Tick Size = Tag 16552 (ExchTickSize)
      P = price in Points (decimal) for which the tick size is required
      for (int i = 0; i < Tag 16456 (NumTickTblEntries); i++)
      {
        if ( P < (Tag 16458 (MaxPrice) for row i) )
        {
          Tick Size (for price P) = Base Tick Size * (Tag 16457 (NumTicks) for row i)
          Tick Value (for price P) = Tick Size (for price P) * Tag 16554 (ExchPointValue)
          exit loop
        }
      }
    }
    

Working with spreads and strategies

When a FIX client requests a security definition for a spread or strategy,
TT FIX responds by sending:

  • A Security Definition (d) for the spread itself. A leg repeating group
    exists for each leg of the spread. Tag 555 (NoLegs) is set to the total
    number of leg repeating groups (spread legs) associated with the spread.
  • One Security Definition (d) for each leg of the spread.

Security Definition Request (c) Message

Security Definition Request (c) Message

Purpose

Used to request contract information

Message Direction

From a FIX client to the TT FIX

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Security Definition Request (c) message is used by FIX clients to request contract data.

You can filter your security definitions so that TT FIX supplies only those instruments that match the
specified values for one or more of the following tags:

  • Tag 55 (Symbol)
  • Tag 100 (ExDestination)
  • Tag 167 (SecurityType)
  • Tag 207 (SecurityExchange)
  • Tag 48 (SecurityID)

    If Tag 48 (SecurityID) is provided, you must also provide Tag 207 (SecurityExchange).

Sending a Security Definition Request (c) message instructs TT FIX to subscribe for contracts that match the
filter criteria. TT FIX sends Security Definition (d) messages for all matching contracts and sends new Security
Definition (d)
messages if any of the contract details, such as tick size, change. Additionally, if
a market adds a new contract that matches the filter criteria, TT FIX automatically sends a Security
Definition (d)
message for the new contract.

TT FIX uses AND logic to build the query, so specifying multiple tags reduces the matched securities. If you
send none of the tags in the request, TT FIX returns all securities for all visible markets.

Note: If TT FIX finds no contracts that match the specified filter, it sends no response
back to the FIX client

Related Information

Security
Definition (d)

Security Status (f) Message

Security Status (f) Message

Purpose

Used to return the current trading status of a security

Message Direction

From TT FIX to FIX client

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Security Status (f) message is used by TT FIX Adapter to respond to a
Security Status Request (e) message. The message indicates the current
trading status of an instrument.

Related Information

Security Status Request (e)

Security Status Request (e) Message

Security Status Request (e) Message

Purpose

Used to request the status of a product

Message Direction

From FIX client to TT FIX

Tag Directory

Click the links below to navigate to the documentation for that tag.

Message Notes

The Security Status Request (e) message is used by FIX clients to request
the current status of a particular product.

Related Information

Security Status (f)

Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

Analytics

This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.

Keeping this cookie enabled helps us to improve our website.

Marketing

This website uses the following additional cookies:

(List the cookies that you are using on the website here.)