Revision History

Date	Description

Date	Description
Wednesday, November 20, 2024	Added certification requirements.
Friday, November 1, 2024	Replaced Failover with Google Cloud Regions and Resiliency
Friday, August 9, 2024	Updated details on Certain IDs, timestamps, and trade ordering "The value in the field TrdCaptRpt/@LastUpdateTm (tag 779) may not match between the current and GC hosted environments. Additionally, the trade ordering may not match between the current and GC hosted environments." Updated operations in regions "CME STP FIXML will operate in multiple GC regions. In the event of a GC failover, there will be no lag in RTO time. Clients can continue to connect to the same URL on GC as they were connected prior to the failover. If a failover occurs, clients will receive the following error message response to their next polling request indicating that they must resubmit their subscription request to the API." Updated definition of TrdCaptRpt/@LastUpdateTm "Updated definition for The value in the field TrdCaptRpt/@LastUpdateTm (tag 779) may not match between the current and GC hosted environments. Additionally, the trade ordering may not match between the current and GC hosted environments."
Wednesday, June 5, 2024	Initial publication of client impact topic.

Key Events and Dates

Date	Milestone

Date	Milestone
Thursday, June 20, 2024	New Release CME STP FIXML API
Sunday, July 28, 2024	Production CME STP FIXML API
Sunday, November 3, 2024	Expected Client Completion CME STP FIXML API
Monday, December 9, 2024	GC regional switch certification available.

Onboarding

CME STP FIXML on Google Cloud will not require separate or additional client onboarding.

Authorization and Entitlement

Clients can continue to use existing API IDs.
CME STP FIXML will continue to use Basic Authorization.
Entitlement will be handled internally by CME Group so that clients do not need to make any changes.

Testing and Certification

Clients that have previously certified their systems STP FIXML messaging are not required to perform a new certification.

Effective Monday, December 9, 2024, a mandatory certification of regional switch processing will be available to client systems for CME STP FIXML on Google Cloud.

This certification is not a pre-requisite for clients migrating to CME STP FIXML on Google Cloud, however, it is mandatory for client systems to complete the certification by Monday, March 31, 2025.

CME Group recommends that clients test CME STP functionality with the Google Cloud instance.

Connectivity

Clients can connect via the following options:

New Release Environment

Connectivity Type	Asset Class	Current Service URL	New Service URL (GC)

Connectivity Type

Asset Class

Current Service URL

New Service URL (GC)

Internet (only)

URL uses certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required.

All

https://servicesnr.cmegroup.com/cmestp/query

https://posttrade.api.uat.cmegroup.com/cmestp/query

Production Environment

Connectivity Type	Asset Class	Current Service URL	New Service URL (GC)

Connectivity Type

Asset Class

Current Service URL

New Service URL (GC)

Internet

URL uses certificates signed by an official trusted Certificate Authority (CA). Additional certificates are not required.

All

https://services.cmegroup.com/cmestp/query

https://posttrade.api.cmegroup.com/cmestp/query

CME STP FIXML uses x-cme-token HTTP variable for continuation of queries and subscriptions. Tokens are valid only for the service (current/GC) in which it was issued.

Both service URLs will be available in parallel. During this period, clients can view the same trade information from both endpoints.

The value in the field TrdCaptRpt/@LastUpdateTm (tag 779) may not match between the current and GC hosted environments. Additionally, the trade ordering may not match between the current and GC hosted environments.

During the parallel period, the same trade data will be available on both services. Clients must take steps to avoid double booking trades within their systems.

CME STP FIXML API Differences

There will be no changes to the CME STP FIXML server and client message payload.

Google Cloud Regions and Resiliency

CME STP FIXML will operate in two GC regions, Eastern and Central United States. Client systems will connect to the same service URL, regardless of which region is active.

Clients should note that the x-cme-token, which is used by client systems for ongoing subscriptions and for multi-batch queries, will not be valid across regions. Upon regional failover, users will receive a TradeCaptureReportRequestAck with the attribute @txt="x-cme-token is no longer valid. Please initiate a new subscription".

Information related to Trade Queries and Subscriptions, including token management and duplicate message detection is available in CME STP FIXML Core.

Contact Information

For technical development support, contact Certification Support for Electronic Trading (CSET).

For production requests, contact the Global Command Center (GCC).

For all other inquiries, contact Global Account Management (GAM).