{"id":7148,"date":"2025-08-28T22:36:12","date_gmt":"2025-08-29T03:36:12","guid":{"rendered":"https:\/\/librarytestdev.wpenginepowered.com\/?post_type=doc&#038;p=7148"},"modified":"2026-09-09T09:10:50","modified_gmt":"2026-09-09T14:10:50","slug":"market-data-message-flows","status":"publish","type":"doc","link":"https:\/\/library-staging.tradingtechnologies.com\/tt-fix\/tt-fix-market-data\/tt-fix-message-conversations-tt-fix-market-data\/market-data-message-flows\/","title":{"rendered":"Market Data Message Flows"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A FIX client starts a FIX Market Data session by sending a <a href=\"\/tt-fix\/general\/Msg_Logon_A.html\">Logon (A)<\/a> message to TT FIX and ends the session by calling the <a href=\"\/tt-fix\/general\/Msg_Logout_5.html\">Logout (5)<\/a> message. While connected to a FIX Market Data session, a FIX client engages in a series of message conversations (requests and responses) with TT FIX to access information about tradable instruments. Typically, market data message conversations involve the following request and response messages.<\/p>\n\n\n<?xml encoding=\"utf-8\" ?><figure class=\"wp-block-table\"><table class=\"has-fixed-layout table table-striped table-bordered\"><tbody><tr><th>Requests<\/th><th>Responses<\/th><\/tr><tr><td><a href=\"\/tt-fix\/market-data\/Msg_MarketDataRequest_V.html\">Market Data Request (V)<\/a><br><a href=\"\/tt-fix\/market-data\/Msg_SecurityDefinitionRequest_c.html\">Security Definition Request (c)<\/a><br><a href=\"\/tt-fix\/market-data\/Msg_SecurityStatusRequest_e.html\">Order Cancel Request (F)<\/a><\/td><td><a href=\"\/tt-fix\/market-data\/Msg_MarketDataSnapshot_W.html\">Market Data Snapshot (W)<\/a><br><a href=\"\/tt-fix\/market-data\/Msg_MarketDataIncrementalRefresh_X.html\">Market Data Incrementatl Refresh (X)<\/a><br><a href=\"\/tt-fix\/market-data\/Msg_MarketDataRequestReject_Y.html\">Market Data Reject (Y)<\/a><br><a href=\"\/tt-fix\/market-data\/Msg_SecurityDefinition_d.html\">Security Definition (d)<\/a><br><a href=\"\/tt-fix\/market-data\/Msg_SecurityStatus_f.html\">Security Status (f)<\/a>\t\t<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Getting Details about Instruments<\/h2>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/08\/security-definition-flow.png\" alt=\"\"\/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The security definition message flow begins with a FIX client sending a <a href=\"\/tt-fix\/market-data\/Msg_SecurityDefinitionRequest_c.html\">Security Definition Request (c)<\/a> message with the desired filtering criteria.\t<\/li>\n\n\n\n<li>For each instrument that matches the filtering criteria, the exchange responds with a <a href=\"\/tt-fix\/market-data\/Msg_SecurityDefinition_d.html\">Security Definition (d)<\/a> message with the details about the instrument.<br><br>Sending a <a href=\"\/tt-fix\/market-data\/Msg_SecurityDefinitionRequest_c.html\">Security Definition Request (c)<\/a> message instructs TT FIX to subscribe for contracts that match the filter criteria.<\/li>\n\n\n\n<li>When the exchange makes any changes to the instrument details, such as the tick size, TT FIX sends another <a href=\"\/tt-fix\/market-data\/Msg_SecurityDefinition_d.html\">Security Definition (d)<\/a> message for the updated instrument.\t<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Monitoring the Trading Status of an Instrument<\/h2>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/08\/security-status-flow-scaled.png\" alt=\"\"\/><\/figure>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The security status message flow begins with a FIX client sending a <a href=\"\/tt-fix\/market-data\/Msg_SecurityStatusRequest_e.html\">Security Status Request (e)<\/a> message with the desired instrument and subscription type.\n<ul class=\"wp-block-list\">\n<li>(1A) To get a single snapshot, the FIX client sets 263=0 in the request.\t\t\t<\/li>\n\n\n\n<li>(1B) To get a single snapshot and subscribe for future status changes, the FIX client sets 263=1 in the request.\t\t<\/li>\n\n\n\n<li>(1C) To cancel a subsription, the FIX client sets 263=2 in the request.<br>\t\t\t\t\t<br>The message flow is complete.\t\t\t<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>TT FIX sends a <a href=\"\/tt-fix\/market-data\/Msg_SecurityStatus_f.html\">Security Status (f)<\/a> message for the requested instrument.\n<ul class=\"wp-block-list\">\n<li>(2A) TT FIX sends the current trading status of the instrument.<br>\t\t\t\t\t<br>The message flow is complete.\t<\/li>\n\n\n\n<li>(2B) TT FIX sends the current trading status of the instrument and subscribes for status updates. When an update occurs, TT FIX sends a new <a href=\"\/tt-fix\/market-data\/Msg_SecurityStatus_f.html\">Security Status (f)<\/a> message with the new information.\t\t\t<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Requesting Market Data for Instruments<\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"626\" height=\"530\" src=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/08\/market-data-flow-1.png\" alt=\"\" class=\"wp-image-60677\" srcset=\"https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/08\/market-data-flow-1.png 626w, https:\/\/library-staging.tradingtechnologies.com\/wp-content\/uploads\/2025\/08\/market-data-flow-1-300x254.png 300w\" sizes=\"auto, (max-width: 626px) 100vw, 626px\" \/><\/figure>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The market data message flow begins with a FIX client sending a <a href=\"\/tt-fix\/market-data\/Msg_MarketDataRequest_V.html\">Market Data Request (V)<\/a> message with the desired instrument and subscription type.\n<ul class=\"wp-block-list\">\n<li>(1A) The FIX client requests one snapshot of market data for an instrument.\t\t\t<\/li>\n\n\n\n<li>(1B) The FIX client subscribes for market data for an instruments and requests to receive all market data, even it it has not changed.\t\t<\/li>\n\n\n\n<li>(1C) The FIX client subscribes for market data for an instruments and requests to receive only market data that has changed.\t\t\t<\/li>\n\n\n\n<li>(1D) The FIX client cancels the market data subscription.<br>\t\t\t\t\t<br>The message flow is complete.\t\t<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>TT FIX sends <a href=\"\/tt-fix\/market-data\/Msg_MarketDataRequestReject_Y.html\">Market Data Reject (Y)<\/a> if it cannot fulfill the request for market data, such as specifying an invalid instrument.\t<\/li>\n\n\n\n<li>TT sends a <a href=\"\/tt-fix\/market-data\/Msg_MarketDataSnapshot_W.html\">Market Data Snapshot (W)<\/a> message.\n<ul class=\"wp-block-list\">\n<li>(3A) For a snapshot update type (263=0), the message flow is complete.\t<\/li>\n\n\n\n<li>(3B) For a subscription update type (263=1) with a request for full updates (265=0), TT continues to send <a href=\"\/tt-fix\/market-data\/Msg_MarketDataSnapshot_W.html\">Market Data Snapshot (W)<\/a> messages each time the market data changes.\t\t<\/li>\n\n\n\n<li>(3C) For a subscription update type (263=1) with a request for incremental updates (265=1), TT sends one <a href=\"\/tt-fix\/market-data\/Msg_MarketDataSnapshot_W.html\">Market Data Snapshot (W)<\/a> message.\t\t<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>As market data changes for the instrument, TT continues to send a <a href=\"\/tt-fix\/market-data\/Msg_MarketDataIncrementalRefresh_X.html\">Market Data Incremental Refresh (X)<\/a> message.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p class=\"wp-block-paragraph\">A FIX client starts a FIX Market Data session by sending a <a href=\"\/tt-fix\/general\/Msg_Logon_A.html\">Logon (A)<\/a> message to TT FIX and ends the session by calling the <a href=\"\/tt-fix\/general\/Msg_Logout_5.html\">Logout (5)<\/a> message. While connected to a FIX Market Data session, a FIX client engages in a series of message conversations (requests and responses) with TT FIX to access information about tradable instruments. Typically, market data message conversations involve the following request and response messages.<\/p>\n<p><?xml encoding=\"utf-8\" ?><\/p>\n<figure class=\"wp-block-table\">\n<table class=\"has-fixed-layout table table-striped table-bordered\">\n<tbody>\n<tr>\n<th>Requests<\/th>\n<th>Responses<\/th>\n<\/tr>\n<tr>\n<td><a href=\"\/tt-fix\/market-data\/Msg_MarketDataRequest_V.html\">Market Data Request (V)<\/a><br \/><a href=\"\/tt-fix\/market-data\/Msg_SecurityDefinitionRequest_c.html\">Security Definition Request (c)<\/a><br \/><a href=\"\/tt-fix\/market-data\/Msg_SecurityStatusRequest_e.html\">Order Cancel Request (F)<\/a><\/td>\n<td><a href=\"\/tt-fix\/market-data\/Msg_MarketDataSnapshot_W.html\">Market Data Snapshot (W)<\/a><br \/><a href=\"\/tt-fix\/market-data\/Msg_MarketDataIncrementalRefresh_X.html\">Market Data Incrementatl Refresh (X)<\/a><br \/><a href=\"\/tt-fix\/market-data\/Msg_MarketDataRequestReject_Y.html\">Market Data Reject (Y)<\/a><br \/><a href=\"\/tt-fix\/market-data\/Msg_SecurityDefinition_d.html\">Security Definition (d)<\/a><br \/><a href=\"\/tt-fix\/market-data\/Msg_SecurityStatus_f.html\">Security Status (f)<\/a>\t\t<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n<h2 class=\"wp-block-heading\">Getting Details about Instruments<\/h2>\n<p class=\"wp-block-paragraph\">\n<h2 class=\"wp-block-heading\">Monitoring the Trading Status of an Instrument<\/h2>\n<h2 class=\"wp-block-heading\">Requesting Market Data for Instruments<\/h2>\n","protected":false},"author":2,"template":"","meta":{"_acf_changed":false,"footnotes":""},"docs-category":[478],"class_list":["post-7148","doc","type-doc","status-publish","hentry","docs-category-tt-fix-message-conversations-tt-fix-market-data"],"acf":[],"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7148","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc"}],"about":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/types\/doc"}],"author":[{"embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/users\/2"}],"version-history":[{"count":6,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7148\/revisions"}],"predecessor-version":[{"id":60679,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7148\/revisions\/60679"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=7148"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=7148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}