{"id":7065,"date":"2025-08-28T22:35:56","date_gmt":"2025-08-29T03:35:56","guid":{"rendered":"https:\/\/librarytestdev.wpenginepowered.com\/?post_type=doc&p=7065"},"modified":"2025-09-25T10:45:57","modified_gmt":"2025-09-25T15:45:57","slug":"fix-strategy-creation-and-rfq-support","status":"publish","type":"doc","link":"https:\/\/library-staging.tradingtechnologies.com\/tt-fix\/tt-fix-order-routing\/overview-tt-fix-order-routing\/fix-strategy-creation-and-rfq-support\/","title":{"rendered":"FIX Strategy Creation and RFQ Support"},"content":{"rendered":"\n

Overview<\/h2>\n\n\n\n

TT FIX Order Router supports submitting Security Definition Request (Tag 35=c)<\/a> messages to create strategies and Quote Request (Tag 35=R)<\/a> messages for Request for Quote (RFQ) functionality.<\/p>\n\n\n\n

Strategy Creation<\/h3>\n\n\n\n

The Security Definition Request (Tag 35=c)<\/a> defines a specific security at the exchange. You can define a multileg security made up of one or more instrument legs.<\/p>\n\n\n\n

Once you submit the request, TT detects if the security already exists in the system and sends a Security Definition (Tag 35=d)<\/a> message for the instrument. If the instrument does not exist, the FIX Order Routing service forwards the request and waits for a response from the exchange.<\/p>\n\n\n\n

Strategy Creation – Success<\/h4>\n\n\n\n

When an instrument is created successfully, FIX Order Routing service responds with a Security Definition (Tag 35=d)<\/a> message with the SecurityResponseType (Tag 323)<\/a> set to either:<\/p>\n\n\n\n

323=1: Accept Instrument proposal as-is<\/p>\n\n\n\n

— or — <\/p>\n\n\n\n

323=2: Accept Instrument proposal w\/ changes indicated<\/p>\n\n\n\n

Strategy Creation – Reject<\/h4>\n\n\n\n

If the instrument is not created successfully, the FIX Order Routing service responds with a Security Definition (Tag 35=d)<\/a> message and SecurityResponseType (Tag 323)<\/a> set to:<\/p>\n\n\n\n

323=5: Reject Instrument Proposal<\/p>\n\n\n\n

Security Definition Changes<\/h4>\n\n\n\n

The Security Definition Request (Tag 35=c)<\/a> message has been updated to match the Instrument and InstrumentLeg components as defined on the Security Definition (Tag 35=d)<\/a> message.<\/p>\n\n\n\n

Note<\/span>\n

The new tags added to the Security Definition Request (Tag 35=c) are only valid when submitting requests via FIX Order Routing sessions.<\/p>\n<\/div>\n\n\n\n

Request for Quote (RFQ)<\/h3>\n\n\n\n

The Quote Request (Tag 35=R)<\/a> message is used to submit Request for Quotes (RFQs) from market makers and brokers in the marketplace prior placing an order. This occurs commonly for multileg strategies where there is insufficient liquidity to get the best price for the instrument.<\/p>\n\n\n\n

Request for Quote – Success<\/h4>\n\n\n\n

For successful RFQ requests, the FIX Order Session sends a Quote Request Response (Tag 35=b)<\/a> message with the following values:<\/p>\n\n\n\n

QuoteAckStatus (Tag 16859): equals 0, “ok”.<\/p>\n\n\n\n

Request for Quote – Reject<\/h4>\n\n\n\n

If the RFQ request is unsuccessful for any reason, the FIX Order Session sends a Quote Request Response (Tag 35=b)<\/a> message with the following values:<\/p>\n\n\n\n

QuoteReqID (Tag 131): equals the unique ID for the request.<\/p>\n\n\n\n

QuoteRejectReason (Tag 300): equals the reason for the reject.<\/p>\n\n\n\n

Quote Response Changes<\/h4>\n\n\n\n

Quote response messages (Quote Request (Tag 35=R)<\/a>) are also sent via the FIX Market Data feed to both API and client applications. Quote responses are not sent over the FIX Order Routing session.<\/p>\n\n\n\n

Note<\/span>\n

The new tags added to the (R) message are valid for use in submission of request messages to FIX Order Routing sessions only. FIX Market Data sessions that subscribe for (R) messages are not impacted by the schema change.<\/p>\n<\/div>\n\n\n\n

FIX Schema Changes<\/h2>\n\n\n\n

The following section highlights the specific FIX schema changes to support Strategy Creation and Request for Quote\n (RFQ) functionality.<\/p>\n\n\n\n

Message type (35=c) – SecurityDefinitionRequest<\/h3>\n\n\n\n

The Security Definition Request (35=c) message sent via the FIX Order Routing Service includes a number of tags to support strategy creation and request for quote functionality. These tags are only included with Order Routing Security Definition Request (35=c) messages and do not appear in the FIX Market Data service.<\/p>\n\n\n

\n
\n\n \n
\n
\n \n <\/div>\n\n <\/div>\n\n \n
<\/div>\n <\/div>\n \n
\n
\n \n \n \n
\n Message type (35=c) – SecurityDefinitionRequest <\/caption>\n
Tag<\/th>Name<\/th>Type<\/th>Comment<\/th> <\/tr>\n <\/thead>\n
1<\/svg><\/a><\/td>Account<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

762<\/svg><\/a><\/td>SecuritySubType<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n
\nRequired for certain exchanges. If not present, the exchange may reject the request.<\/td><\/tr>

555<\/svg><\/a><\/td>NoLegs<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n
\nThe NoLegs repeating group and its fields are introduced to support Strategy creation via FIX Order Routing by passing individual underlying legs via the 6xx repeating groups.<\/td><\/tr>

566<\/svg><\/a><\/td>LegPrice<\/td>PRICE<\/td>\u2014<\/td><\/tr>
600<\/svg><\/a><\/td>LegSymbol<\/td>STRING<\/td>\u2014<\/td><\/tr>
602<\/svg><\/a><\/td>LegSecurityID<\/td>STRING<\/td>\u2014<\/td><\/tr>
603<\/svg><\/a><\/td>LegIDSource<\/td>STRING<\/td>\u2014<\/td><\/tr>
607<\/svg><\/a><\/td>LegProduct<\/td>INT<\/td>\u2014<\/td><\/tr>
608<\/svg><\/a><\/td>LegCFICode<\/td>STRING<\/td>\u2014<\/td><\/tr>
609<\/svg><\/a><\/td>LegSecurityType<\/td>STRING<\/td>\u2014<\/td><\/tr>
610<\/svg><\/a><\/td>LegMaturityMonthYear<\/td>MONTHYEAR<\/td>\u2014<\/td><\/tr>
611<\/svg><\/a><\/td>LegMaturityDate<\/td>LOCALMKTDATE<\/td>\u2014<\/td><\/tr>
612<\/svg><\/a><\/td>LegStrikePrice<\/td>PRICE<\/td>\u2014<\/td><\/tr>
613<\/svg><\/a><\/td>LegOptAttribute<\/td>CHAR<\/td>\u2014<\/td><\/tr>
616<\/svg><\/a><\/td>LegSecurityExchange<\/td>EXCHANGE<\/td>\u2014<\/td><\/tr>
623<\/svg><\/a><\/td>LegRatioQty<\/td>FLOAT<\/td>\u2014<\/td><\/tr>
624<\/svg><\/a><\/td>LegSide<\/td>CHAR<\/td>\u2014<\/td><\/tr>
764<\/svg><\/a><\/td>LegSecuritySubType<\/td>STRING<\/td>\u2014<\/td><\/tr>
811<\/svg><\/a><\/td>OptionDelta<\/td>FLOAT<\/td>\u2014<\/td><\/tr>
1358<\/svg><\/a><\/td>LegPutOrCall<\/td>INT<\/td>\u2014<\/td><\/tr>
18212<\/svg><\/a><\/td>LegDeliveryTerm<\/td>CHAR<\/td>\u2014<\/td><\/tr>
18213<\/svg><\/a><\/td>LegDeliveryDate<\/td>LOCALMKTDATE<\/td>\u2014<\/td><\/tr>
18314<\/svg><\/a><\/td>LegMaturityDay<\/td>DAYOFMONTH<\/td>\u2014<\/td><\/tr>
18100<\/svg><\/a><\/td>LegExDestination<\/td>EXCHANGE<\/td>\u2014<\/td><\/tr>
18224<\/svg><\/a><\/td>LegContractYearMonth<\/td>STRING<\/td>\u2014<\/td><\/tr> <\/tbody>\n <\/table><\/div>\n <\/figure>\n <\/div>\n\n\n

Message type (35=R) – Quote Request<\/h3>\n\n\n
\n
\n\n \n
\n
\n \n <\/div>\n\n <\/div>\n\n \n
<\/div>\n <\/div>\n \n
\n
\n \n \n \n
\n Message type (35=R) – Quote Request <\/caption>\n
Tag<\/th>Name<\/th>Type<\/th>Comment<\/th> <\/tr>\n <\/thead>\n
22<\/svg><\/a><\/td>IDSource<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

1<\/svg><\/a><\/td>Account<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

18102<\/svg><\/a><\/td>UserID<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

146<\/svg><\/a><\/td>NoRelatedSym<\/td>NUMINGROUP<\/td>\u2014<\/td><\/tr>
454<\/svg><\/a><\/td>NoSecurityAltID<\/td>NUMINGROUP<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n
\nAdded to support multi leg lookup.<\/td><\/tr>

455<\/svg><\/a><\/td>SecurityAltID<\/td>STRING<\/td>\u2014<\/td><\/tr>
16207<\/svg><\/a><\/td>BloombergSecurityExchange<\/td>STRING<\/td>\u2014<\/td><\/tr>
555<\/svg><\/a><\/td>NoLegs<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n
\nTo support multi leg lookup similar to other messages like NewOrderMultiLeg etc.<\/td><\/tr>

566<\/svg><\/a><\/td>LegPrice<\/td>PRICE<\/td>\u2014<\/td><\/tr>
600<\/svg><\/a><\/td>LegSymbol<\/td>STRING<\/td>\u2014<\/td><\/tr>
602<\/svg><\/a><\/td>LegSecurityID<\/td>STRING<\/td>\u2014<\/td><\/tr>
603<\/svg><\/a><\/td>LegIDSource<\/td>STRING<\/td>\u2014<\/td><\/tr>
607<\/svg><\/a><\/td>LegProduct<\/td>INT<\/td>\u2014<\/td><\/tr>
608<\/svg><\/a><\/td>LegCFICode<\/td>STRING<\/td>\u2014<\/td><\/tr>
609<\/svg><\/a><\/td>LegSecurityType<\/td>STRING<\/td>\u2014<\/td><\/tr>
610<\/svg><\/a><\/td>LegMaturityMonthYear<\/td>MONTHYEAR<\/td>\u2014<\/td><\/tr>
611<\/svg><\/a><\/td>LegMaturityDate<\/td>LOCALMKTDATE<\/td>\u2014<\/td><\/tr>
612<\/svg><\/a><\/td>LegStrikePrice<\/td>PRICE<\/td>\u2014<\/td><\/tr>
613<\/svg><\/a><\/td>LegOptAttribute<\/td>CHAR<\/td>\u2014<\/td><\/tr>
616<\/svg><\/a><\/td>LegSecurityExchange<\/td>EXCHANGE<\/td>\u2014<\/td><\/tr>
623<\/svg><\/a><\/td>LegRatioQty<\/td>FLOAT<\/td>\u2014<\/td><\/tr>
624<\/svg><\/a><\/td>LegSide<\/td>CHAR<\/td>\u2014<\/td><\/tr>
764<\/svg><\/a><\/td>LegSecuritySubType<\/td>STRING<\/td>\u2014<\/td><\/tr>
620<\/svg><\/a><\/td>LegSecurityDesc<\/td>STRING<\/td>\u2014<\/td><\/tr>
1358<\/svg><\/a><\/td>LegPutOrCall<\/td>INT<\/td>\u2014<\/td><\/tr>
18212<\/svg><\/a><\/td>LegDeliveryTerm<\/td>CHAR<\/td>\u2014<\/td><\/tr>
18213<\/svg><\/a><\/td>LegDeliveryDate<\/td>LOCALMKTDATE<\/td>\u2014<\/td><\/tr>
18314<\/svg><\/a><\/td>LegMaturityDay<\/td>DAYOFMONTH<\/td>\u2014<\/td><\/tr>
18100<\/svg><\/a><\/td>LegExDestination<\/td>EXCHANGE<\/td>\u2014<\/td><\/tr>
556<\/svg><\/a><\/td>LegCurrency<\/td>CURRENCY<\/td>\u2014<\/td><\/tr>
604<\/svg><\/a><\/td>NoLegSecurityAltID<\/td>NUMINGROUP<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n
\nTo support multi leg lookup similar to other messages like NewOrderMultiLeg etc.<\/td><\/tr>

605<\/svg><\/a><\/td>LegSecurityAltID<\/td>STRING<\/td>\u2014<\/td><\/tr>
606<\/svg><\/a><\/td>LegSecurityAltIDSource<\/td>STRING<\/td>\u2014<\/td><\/tr>
16616<\/svg><\/a><\/td>LegBloombergSecurityExchange<\/td>STRING<\/td>\u2014<\/td><\/tr> <\/tbody>\n <\/table><\/div>\n <\/figure>\n <\/div>\n\n\n

New message type (35=b) – Quote Request Response\n (ADDED)<\/h3>\n\n\n
\n
\n\n \n
\n
\n \n <\/div>\n\n <\/div>\n\n \n
<\/div>\n <\/div>\n \n
\n
\n \n \n \n
\n message type (35=b) – Quote Request Response <\/caption>\n
Tag<\/th>Name<\/th>Type<\/th>Custom Column<\/th> <\/tr>\n <\/thead>\n
131<\/svg><\/a><\/td>QuoteReqID<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n
\nMaps to the QuoteReqID (tag 131) in the RFQ request (35=R)<\/td><\/tr>

1<\/svg><\/a><\/td>Account<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

17<\/svg><\/a><\/td>ExecID<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

16859<\/svg><\/a><\/td>QuoteAckStatus<\/td>INT<\/td>Added new field
\n
\nMappings:
\n0:<\/strong> QUOTE_REQUEST_STATUS_OK
\n5:<\/strong> QUOTE_REQUEST_STATUS_REJECTED<\/td><\/tr>
18101<\/svg><\/a><\/td>AccountID<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

18102<\/svg><\/a><\/td>UserID<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

16117<\/svg><\/a><\/td>OrderSource<\/td>INT<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

1028<\/svg><\/a><\/td>ManualOrderIndicator<\/td>BOOLEAN<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

37<\/svg><\/a><\/td>OrderID<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

1724<\/svg><\/a><\/td>OrderOrigination<\/td>INT<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

38<\/svg><\/a><\/td>OrderQty<\/td>QTY<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

198<\/svg><\/a><\/td>SecondaryOrderID<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

107<\/svg><\/a><\/td>SecurityDesc<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

54<\/svg><\/a><\/td>Side<\/td>CHAR<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

58<\/svg><\/a><\/td>Text<\/td>STRING<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

60<\/svg><\/a><\/td>TransactTime<\/td>UTCTIMESTAMP<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr>

582<\/svg><\/a><\/td>CustOrderCapacity<\/td>INT<\/td>\n

Added to message for FIX Order Routing sessions.<\/p>\n<\/td><\/tr> <\/tbody>\n <\/table><\/div>\n <\/figure>\n <\/div>","protected":false},"excerpt":{"rendered":"

Overview<\/h2>\n

TT FIX Order Router supports submitting Security Definition Request (Tag 35=c)<\/a> messages to create strategies and Quote Request (Tag 35=R)<\/a> messages for Request for Quote (RFQ) functionality.<\/p>\n

Strategy Creation<\/h3>\n

The Security Definition Request (Tag 35=c)<\/a> defines a specific security at the exchange. You can define a multileg security made up of one or more instrument legs.<\/p>\n

Once you submit the request, TT detects if the security already exists in the system and sends a Security Definition (Tag 35=d)<\/a> message for the instrument. If the instrument does not exist, the FIX Order Routing service forwards the request and waits for a response from the exchange.<\/p>\n

Strategy Creation – Success<\/h4>\n

When an instrument is created successfully, FIX Order Routing service responds with a Security Definition (Tag 35=d)<\/a> message with the SecurityResponseType (Tag 323)<\/a> set to either:<\/p>\n

323=1: Accept Instrument proposal as-is<\/p>\n

— or — <\/p>\n

323=2: Accept Instrument proposal w\/ changes indicated<\/p>\n

Strategy Creation – Reject<\/h4>\n

If the instrument is not created successfully, the FIX Order Routing service responds with a Security Definition (Tag 35=d)<\/a> message and SecurityResponseType (Tag 323)<\/a> set to:<\/p>\n

323=5: Reject Instrument Proposal<\/p>\n

Security Definition Changes<\/h4>\n

The Security Definition Request (Tag 35=c)<\/a> message has been updated to match the Instrument and InstrumentLeg components as defined on the Security Definition (Tag 35=d)<\/a> message.<\/p>\n

Request for Quote (RFQ)<\/h3>\n

The Quote Request (Tag 35=R)<\/a> message is used to submit Request for Quotes (RFQs) from market makers and brokers in the marketplace prior placing an order. This occurs commonly for multileg strategies where there is insufficient liquidity to get the best price for the instrument.<\/p>\n

Request for Quote – Success<\/h4>\n

For successful RFQ requests, the FIX Order Session sends a Quote Request Response (Tag 35=b)<\/a> message with the following values:<\/p>\n

QuoteAckStatus (Tag 16859): equals 0, “ok”.<\/p>\n

Request for Quote – Reject<\/h4>\n

If the RFQ request is unsuccessful for any reason, the FIX Order Session sends a Quote Request Response (Tag 35=b)<\/a> message with the following values:<\/p>\n

QuoteReqID (Tag 131): equals the unique ID for the request.<\/p>\n

QuoteRejectReason (Tag 300): equals the reason for the reject.<\/p>\n

Quote Response Changes<\/h4>\n

Quote response messages (Quote Request (Tag 35=R)<\/a>) are also sent via the FIX Market Data feed to both API and client applications. Quote responses are not sent over the FIX Order Routing session.<\/p>\n

FIX Schema Changes<\/h2>\n

The following section highlights the specific FIX schema changes to support Strategy Creation and Request for Quote
\n (RFQ) functionality.<\/p>\n

Message type (35=c) – SecurityDefinitionRequest<\/h3>\n

The Security Definition Request (35=c) message sent via the FIX Order Routing Service includes a number of tags to support strategy creation and request for quote functionality. These tags are only included with Order Routing Security Definition Request (35=c) messages and do not appear in the FIX Market Data service.<\/p>\n

Message type (35=R) – Quote Request<\/h3>\n

New message type (35=b) – Quote Request Response
\n (ADDED)<\/h3>\n","protected":false},"author":2,"menu_order":1695,"template":"","meta":{"_acf_changed":false,"footnotes":""},"docs-category":[458],"class_list":["post-7065","doc","type-doc","status-publish","hentry","docs-category-overview-tt-fix-order-routing"],"acf":[],"permalink_manager":null,"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7065","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\/7065\/revisions"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=7065"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=7065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}