{"id":7104,"date":"2025-08-28T22:36:04","date_gmt":"2025-08-29T03:36:04","guid":{"rendered":"https:\/\/librarytestdev.wpenginepowered.com\/?post_type=doc&#038;p=7104"},"modified":"2025-09-14T19:27:04","modified_gmt":"2025-09-15T00:27:04","slug":"message-structure-message-body-2","status":"publish","type":"doc","link":"https:\/\/library-staging.tradingtechnologies.com\/tt-fix\/tt-fix-gateway\/fix-message-structure-tt-fix-gateway\/message-structure-message-body-2\/","title":{"rendered":"Message structure: Message Body"},"content":{"rendered":"\n\t\t<h2>About the message body<\/h2>\n\t\t<p>The message body contains data specific to the particular message.<\/p>\n\t\t\t<!--\n\t\t<h3>Common components in messages<\/h3>\n\t\t<p>Many messages share a common set of tags. For example, all of the order-related messages contain tags that identify the trader and trading account information. To help identify these shared components, the TT FIX Gateways group the shared tags into the following groups:<\/p>\n\t\t<ul>\n\t\t\t<li><strong>Instrument component block<\/strong>, which contains FIX tags that identify tradeable instruments<\/li>\n\t\t\t<li><strong>Underlying instrument component block<\/strong>, which contains FIX tags that identify legs of multi-leg instruments<\/li>\n\t\t\t<li><strong>Trader component block<\/strong>, which contains FIX tags that identify a trader and corresponding account information<\/li>\n\t\t<\/ul>\n\t\t<h3>Component differences between request and response<\/h3>\n\t\t<p>Component blocks can also differ based on the source of the message, whether a request from the TT FIX Gateways or a response from a third-party FIX acceptor. For example, an instrument component block comprises FIX tags that fully define a product, including its identity, characteristics, and price data. When submitting a request, the TT FIX Gateways need to include only enough tags in the instrument component block to identify uniquely the instrument for the third-party FIX acceptor. When the third-party FIX acceptor sends the response, it includes all of the tags - unlike the request which includes only enough tags to uniquely identify the instrument with the requested information.<\/p>\n\t\t<h3>Component blocks<\/h3>\n\t\t<p>Each FIX message can contain zero or more component blocks. The FIX Protocol uses the component blocks as a convenient way to group a set of FIX tags that might appear in multiple messages.<\/p>\n\t\t<p>The TT FIX Gateways support the following component blocks in a message body:<\/p>\n\t\t<ul>\n\t\t\t<li>Instrument component block for requests<\/li>\n\t\t\t<li><a href=\"InstrumentBlock_Response.html\">Instrument component block for responses<\/a><\/li>\n\t\t\t<li>Underlying instrument component block for requests<\/li>\n\t\t\t<li>Underlying instrument component block for responses<\/li>\n\t\t<\/ul>\n\t\t-->\n\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<h2>About the message body<\/h2>\n<p>The message body contains data specific to the particular message.<\/p>\n<p>\t\t\t<!--\n\t\t\n\n\n\n<h3>Common components in messages<\/h3>\n\n\n\n\n\t\t\n\n\n\n<p>Many messages share a common set of tags. For example, all of the order-related messages contain tags that identify the trader and trading account information. To help identify these shared components, the TT FIX Gateways group the shared tags into the following groups:<\/p>\n\n\n\n\n\t\t\n\n\n\n<ul>\n\t\t\t\n\n\n\n<li><strong>Instrument component block<\/strong>, which contains FIX tags that identify tradeable instruments<\/li>\n\n\n\n\n\t\t\t\n\n\n\n<li><strong>Underlying instrument component block<\/strong>, which contains FIX tags that identify legs of multi-leg instruments<\/li>\n\n\n\n\n\t\t\t\n\n\n\n<li><strong>Trader component block<\/strong>, which contains FIX tags that identify a trader and corresponding account information<\/li>\n\n\n\n\n\t\t<\/ul>\n\n\n\n\n\t\t\n\n\n\n<h3>Component differences between request and response<\/h3>\n\n\n\n\n\t\t\n\n\n\n<p>Component blocks can also differ based on the source of the message, whether a request from the TT FIX Gateways or a response from a third-party FIX acceptor. For example, an instrument component block comprises FIX tags that fully define a product, including its identity, characteristics, and price data. When submitting a request, the TT FIX Gateways need to include only enough tags in the instrument component block to identify uniquely the instrument for the third-party FIX acceptor. When the third-party FIX acceptor sends the response, it includes all of the tags - unlike the request which includes only enough tags to uniquely identify the instrument with the requested information.<\/p>\n\n\n\n\n\t\t\n\n\n\n<h3>Component blocks<\/h3>\n\n\n\n\n\t\t\n\n\n\n<p>Each FIX message can contain zero or more component blocks. The FIX Protocol uses the component blocks as a convenient way to group a set of FIX tags that might appear in multiple messages.<\/p>\n\n\n\n\n\t\t\n\n\n\n<p>The TT FIX Gateways support the following component blocks in a message body:<\/p>\n\n\n\n\n\t\t\n\n\n\n<ul>\n\t\t\t\n\n\n\n<li>Instrument component block for requests<\/li>\n\n\n\n\n\t\t\t\n\n\n\n<li><a href=\"InstrumentBlock_Response.html\">Instrument component block for responses<\/a><\/li>\n\n\n\n\n\t\t\t\n\n\n\n<li>Underlying instrument component block for requests<\/li>\n\n\n\n\n\t\t\t\n\n\n\n<li>Underlying instrument component block for responses<\/li>\n\n\n\n\n\t\t<\/ul>\n\n\n\n\n\t\t--><\/p>\n<p class=\"wp-block-paragraph\">\n","protected":false},"author":2,"template":"","meta":{"_acf_changed":false,"footnotes":""},"docs-category":[464],"class_list":["post-7104","doc","type-doc","status-publish","hentry","docs-category-fix-message-structure-tt-fix-gateway"],"acf":[],"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7104","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":0,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7104\/revisions"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=7104"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=7104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}