Background

360T has upgraded their API Spec to a new version dated March 2025 to improve performance and a few improvisations listed below. 

Affected Venues

• t360_gtx

Changes

Change overview from 360T

1. OrderID, ExecID, MDEntryID on the new gateway is numeric (positive 63-bit Integer); old version sent alphanumeric text.
2. PartyID repeating group no longer contains PartyRole 36 (Entering Trader), only PartyRole 17 and PartyRole 20 for ExecType=F (Trade).
3. Added support for Floating Peg with Discretion, Mid-match, and EDF reference price. This requires a separate session from non-peg orders. Peg session does not support Order Modify currently.
4. Removed support for Stop, Trailing Stop, OCO, ExpireDate, TWAP Algo, AutoTP/SL, Order Status, Order Mass Status.
5. Removed support for Survive-After-Disconnect. All orders are Kill-On-Disconnect.
6. Removed support for Local-Only (18=h) on per-order basis. We do support Local-Only orders (i.e firm or no-last-look) but you need a dedicated session for those.
7. Removed support for SecondaryClOrdID(526), SenderSubID(50), OBOCompID(115), OBOSubID(116) – previously these would be echoed back; now they’re just ignored.
8. Removed support for Account(1). If you need multiple accounts you need to subscribe on separate sessions.
9. Removed Scope(546)=1/2/3 in each MDEntry. If you need to distinguish firm from last-look liquidity, we can give you a dedicated MD session for that.
10. Security List (35=y) initially has all the instruments, but at value date change you will get separate single-entry updates instead of a single many-entry update.

Timeline

The changes are available currently in UAT and Production.

Whisperer clients will see the below listed changes as a part of the API spec upgrade.