ICE is releasing new FIX messages and tags to ICE Trade Capture (ICE FIX TC) and the ICE Private Order Feed (ICE FIX POF) with its Q4 2026 Derivatives Trading Platform Release. ICE will upgrade its Main2 Silo (formerly the Endex Silo) in production on 20 November 2026, with the ICE and LIFFE silos to follow no sooner than February 2027. ICE Trade Capture (ICE FIX TC) is the ICE FIX interface that delivers real-time and historical trade reports; the ICE Private Order Feed (ICE FIX POF) is the ICE FIX interface that delivers real-time and historical order and trade information, including WebICE, FIX Order Server (ICE FIX OS) and Binary Order Entry (ICE BOE) activity. Both run over the FIX protocol, so a client that rejects or mishandles a new message type or tag will see it in its session logs.
In short: ICE adds a strip roll message (Security Status, 35=f), unsolicited Security Definitions for new FLEX strikes, a News message at each new trading session, and SmartOrderID (9080) and SmartOrderType (9081) to ICE FIX TC and ICE FIX POF. The Main2 Silo goes live in production on 20 November 2026. ICE Trade Capture clients must update their FIX dictionary, because the new tags sit in a repeating group. The OnixS SDKs for both interfaces already include the updates.
This article covers the ICE FIX API changes for both interfaces: the tag changes, what each one does to a client application, the rollout schedule, and the OnixS updates we have already released for both interfaces.
What changes in ICE FIX TC and ICE FIX POF in Q4 2026?
ICE lists four changes that apply to both interfaces. Three of them depend on a session setting called PublishMktCreationRealtime (Tag 9010). Set to 1 at logon, it asks ICE to publish market creation events in real time.
Critical Impact Note: SmartOrderID (9080) and SmartOrderType (9081) sit inside a repeating group in the Trade Capture Report, so a TC client without the updated FIX dictionary dialect can fail to parse the report.
| Change | Message and tags | Who receives it | Action ICE asks for |
|---|---|---|---|
| Strip roll notification | Security Status (35=f): Symbol (55)=0, StripType (9200), StripID (9201), StripName (9202), StartDate (916), EndDate (917) | Sessions with PublishMktCreationRealtime (9010)=1 | Add 9200, 9201 and 9202 to the FIX dictionary; validate 35=f handling in AP1 |
| New FLEX strikes from a strip roll | Security Definition (35=d), unsolicited | Sessions with 9010=1 | Validate real-time 35=d handling in AP1 |
| New trading session | News (35=B), Text (58) = one external market type ID; one message per market type | Connected gateway IDs | Review handling of several News messages at session start; validate in AP1 |
| Smart order linkage | SmartOrderID (9080) and SmartOrderType (9081) on POF Execution Report (35=8) and TC Trade Capture Report | Clients that read the fields | TC: add 9080 and 9081 to the dictionary (they sit in a repeating group). POF: add them if used. Validate in AP1 |
How each tag change affects your application
Strip roll notifications. A strip roll creates the next set of contracts for a market strip. ICE now announces each roll with one Security Status message (35=f) at strip level. Symbol (55) is set to 0, so the message identifies a strip, not an instrument. Match StripID (9201) against the strip IDs in your static data to find the affected markets. StripType (9200), StripID (9201) and StripName (9202) are ICE custom tags. StartDate (916) and EndDate (917) give the effective period of the new strip. Those two tags already appear in existing messages; the new part is the 35=f message type that carries them. ICE asks you to add 9200, 9201 and 9202 to your FIX dictionaries; we have made that update in the OnixS SDKs. Any code that expects a resolvable symbol on every message needs a branch for 35=f. The message gives you new strip-level detail, so assess its business impact and change your business logic to use it.
Security definitions for new FLEX strikes. New FLEX option strikes created by a strip roll are tradable the moment they exist. ICE now sends their Security Definition (35=d) unsolicited. Clients on 9010=1 no longer need a Security Definition Request (35=c) to learn about them. Check that your handler accepts a 35=d with no matching request and updates the instrument cache without waiting for a response ID to correlate.
New trading session notification. When a new trading session begins, ICE publishes a News message (35=B) to connected gateway IDs. One message goes out for each affected market type, and Text (58) carries the single external market type ID. You can refresh security definitions and static data for that market type without reconnecting. Expect several News messages in quick succession at session start and make the refresh logic safe to run more than once.
SmartOrderID and SmartOrderType. The POF Execution Report (35=8) and the TC Trade Capture Report now carry SmartOrderID (9080) and SmartOrderType (9081). They link trades generated by WebICE smart orders so you can group them as WebICE does. SmartOrderType values run from 1 (Contingency Order) through 10 (UPS), plus 11 (Unknown). For types 1 to 6 (Contingency Order, TTL, Trailing Stop, OCO, Bracket and GT Datetime), SmartOrderID holds the ClOrderID. For types 7 to 10 (Time Sliced, Randomized Iceberg, Scheduled Order and UPS), it holds the smart order ID. Changing business logic to use the tags is optional. Key your grouping on the pair of 9081 and 9080, and treat 9080 as an opaque identifier.
Silo label. The updated specifications rename the ENDEX exchange silo to MAIN2. ExchangeSilo (9064) keeps the value 1; only the label changes (0 is ICE, 1 is MAIN2, 2 is LIFFE). Configuration screens, logs and reports that print the label need the new name.
When does ICE roll out the changes?
ICE is releasing the changes first to the Main2 Silo, formerly the Endex Silo, and later to the ICE and LIFFE silos.
| Date | Milestone | Scope |
|---|---|---|
| 14 October 2026 | AP1 upgrade to the new release code | Main2 Silo (formerly the Endex Silo) only. Updated conformance scripts and specifications on ICE Service Community. |
| 20 November 2026 | Production upgrade in the evening maintenance window | Main2 Silo only. ICE has dropped the slow rollout it first planned and will announce any change to this date by email and on ICE Service Community. |
| Early December 2026 | AP1 upgrades for the ICE and LIFFE silos | ICE and LIFFE silos, in the AP1 test environment, separately from Main2. ICE will email specific dates. |
| Q1 2027 (earliest February 2027) | Production go-live for the ICE and LIFFE silos | ICE and LIFFE silos. |
ICE has published pre-release specifications for the new messages, and keeps the current production specifications available for reference. ICE will upgrade all applicable Main2 Silo production systems in the evening maintenance window on 20 November 2026.
We recommend that you follow the ICE Service Community and ICE's email updates for any changes.
OnixS updates for the ICE changes
We have released updates to the OnixS directConnect: ICE FIX Trade Capture Handler SDK and the OnixS directConnect: ICE FIX Private Order Feed Handler SDK for the October 2026 specifications: ICE TC version 4.22 and ICE POF version 3.24. The updates cover every platform we support for the two interfaces, and each has its own release notes. The updates include the dictionary changes ICE asks for, so you do not need to make them yourself: the Security Status message type, tags 9200 to 9202, and tags 9080 and 9081.
| OnixS release | Release date | ICE specification | Jira reference |
|---|---|---|---|
| ICE Trade Capture .NET 4.0.0 | 21 October 2026 | ICE TC 4.22 | ITCNCORE-90 |
| ICE Trade Capture .NET Framework 3.0.0 | 21 October 2026 | ICE TC 4.22 | ICETC-751 |
| ICE Trade Capture Java 3.0.1 | 21 October 2026 | ICE TC 4.22 | JAVAICEFIXTC-278 |
| ICE Private Order Feed (POF) .NET 4.0.0 | 27 October 2026 | ICE POF 3.24 | IPOFPNCORE-45 |
| ICE Private Order Feed (POF) .NET Framework 2.0.0 | 27 October 2026 | ICE POF 3.24 | NETICEPOF-248 |
| ICE Private Order Feed (POF) C++ 3.0.0 | 27 October 2026 | ICE POF 3.24 | ICEPOFCPP-55 |
| ICE Private Order Feed (POF) Java 2.0.0 | 27 October 2026 | ICE POF 3.24 | JICEPOF-110 |
The updates include usage reference samples. Each distribution includes the reference implementation samples for its code base: .NET, .NET Framework and Java for ICE Trade Capture, and .NET, .NET Framework, Java and C++ for the ICE Private Order Feed. In those samples we added the updated dialects, and we added a simple Security Status (35=f) message parser to the message processing class, which outputs each message of that type it receives. The samples log on with PublishMktCreationRealtime (Tag 9010) set to 1, so strip roll notifications arrive without extra configuration. Use the samples to see how a session receives and parses the new message, then adapt them for your AP1 tests.
How do I test the ICE tag changes in AP1?
- Log on to AP1 with PublishMktCreationRealtime (Tag 9010) set to 1 and confirm your session accepts a Security Status (35=f) with Symbol 0.
- Confirm an unsolicited Security Definition (35=d) for a new FLEX strike updates your instrument data without a prior 35=c.
- Send several News (35=B) messages at session start and check your static data refresh runs once per market type without a reconnect.
- Replay Execution Reports and Trade Capture Reports with all SmartOrderType values from 1 to 11 and check how your grouping treats 9080 for each.
- Repeat the run for each silo and session type you use, and again if ICE changes the 20 November 2026 production date.
Frequently asked questions
What is SmartOrderID (9080) in ICE FIX? SmartOrderID (9080) and SmartOrderType (9081) link trades generated by WebICE smart orders so you can group them. They appear on the ICE FIX POF Execution Report (35=8) and the ICE FIX TC Trade Capture Report. SmartOrderType takes values from 1 to 11. Treat the SmartOrderID value as opaque.
Do I need to update my ICE Trade Capture dictionary? Yes. SmartOrderID and SmartOrderType sit inside a repeating group in the Trade Capture Report, so a TC client without the updated FIX dictionary dialect can fail to parse the report. Add 9080 and 9081, and add 9200, 9201 and 9202 for the new Security Status message.
What is a Security Status (35=f) message in ICE FIX? It is the new strip roll notification. ICE sends one message per strip, with Symbol (55) set to 0, to sessions that log on with PublishMktCreationRealtime (9010) set to 1. It carries StripType (9200), StripID (9201), StripName (9202), StartDate (916) and EndDate (917).
Does this affect the ICE and LIFFE silos? Yes, later. ICE upgrades the Main2 Silo in production on 20 November 2026. The AP1 test environment upgrades for the ICE and LIFFE silos follow in early December 2026, with production no sooner than February 2027. ICE will email the dates.
Which OnixS SDKs support the ICE changes? ICE Trade Capture .NET 4.0.0, .NET Framework 3.0.0 and Java 3.0.1 support ICE TC 4.22. ICE Private Order Feed .NET 4.0.0, .NET Framework 2.0.0, C++ 3.0.0 and Java 2.0.0 support ICE POF 3.24.
Contact OnixS Support
If you need help with the ICE changes, contact OnixS Support through the OnixS support page.
For a free 30-day evaluation, download the ICE Trade Capture or ICE Private Order Feed Handler SDK, or contact us at sales@onixs.biz.
