{"id":7084,"date":"2025-08-28T22:36:00","date_gmt":"2025-08-29T03:36:00","guid":{"rendered":"https:\/\/librarytestdev.wpenginepowered.com\/?post_type=doc&p=7084"},"modified":"2025-12-11T10:03:05","modified_gmt":"2025-12-11T16:03:05","slug":"new-order-list-e-message","status":"publish","type":"doc","link":"https:\/\/library-staging.tradingtechnologies.com\/tt-fix\/tt-fix-order-routing\/supported-application-messages\/new-order-list-e-message\/","title":{"rendered":"New Order List (E) Message"},"content":{"rendered":"\n

New Order List (E) Message<\/h2>\n\n\n\n
\n

Purpose<\/h3>\n \n

Note<\/span> New Order List (35=E) messages are supported in TT only by the EPEX and Nord Pool exchanges.<\/p> \n\n

Defines a basket of multiple contracts and submits multiple individual orders in a single message. <\/p>\n\n

For each New Order List (35=E) submitted, the exchange will either accept or reject all component orders in the list. Partial accepts or rejects will not be processed. No ack or reject is sent for the New Order List (35=E) message itself.<\/p>\n\n

If the New Order List (35=E) message is accepted, then the FIX client will receive individual new order acknowledgment Execution Reports (39=0; 150=0) for each order in the list. The working component orders must then be managed individually as separate orders.<\/p>\n\n

If the New Order List (35=E) message is rejected, then the FIX client will receive individual new order reject Execution Reports (39=8; 150=8) for each order in the list.<\/p>\n\n

Note<\/span> Time-in-force for the individual orders must be either IOC or FOK. No other TIFs are supported for component orders at this time.<\/p>\n\n <\/div>\n\n\n\n

\n

Message Direction<\/h3>\n

From FIX client to TT FIX<\/p>\n <\/div>\n\n\n\n

Tag Directory<\/h3>\n\n\n\n

Click the links below to navigate to the documentation for that tag.<\/p>\n\n\n

\n
Using the FIX Tag Directory<\/summary>\n