To support the integration of BrokerTec markets with CME Group technology, subject to applicable regulatory approvals, transactions executed on CME Globex, BrokerTec Direct, and registered external deals will be available for consumption on CME STP in both FIX and FIXML formats.
CME STP will support a variety of fixed income transactions, including cash transactions on bonds as well as repurchase transactions (repos) on bonds. These include:
- CME Globex matched:
- US Treasury (UST) Actives
- US Repos
- EU Repos
- European Government Bonds (EGBs)
Customers may entitle vendors to access their data, which will be controlled through entitlement and account configuration.
CME STP will continue to support existing CME Group products and CME Bilateral and Cleared Elsewhere products. See current specifications.
- CME STP supports implied and non-implied Curve Ratio (RV) Spreads for US Treasury Actives, reflected in MLegRptTyp=2 (leg of spread) messages.
- MLegRptTyp=3 (spread) messages are only reflected on non-implied Curve Ratio(RV) spreads messages.
|2/2/2021||Added Production Service Availability section|
CollateralReport - Missing value 8=Replace added to tag 20012-CollateralReportTransactionType
Trade Capture Report – tags 99400, 719, 99401 added for Exercise and Assignment Trades. Not applicable to BrokerTec.
|11/3/2020||Simplified & added clarity to connectivity section.|
|11/3/2020||Added Internet IP.|
|10/23/2020||Added information on x-cme-token size limit|
|10/20/2020||Updated IP information for BrokerTec legacy line connectivity|
|10/13/2020||Added tag 30-LastMkt for TradeCaptureReport(AE) and Collateral Report(BA)|
Added note for Tag 779-LastUpdateTime timestamp value
|10/9/2020||CME STP API Connectivity|
reinstated 20016 MaximumCollateralCount
removed 20016 MaximumCollateralCount
|6/12/2020||Removed note - Trade cancels and adjusts will be addressed in future iterations of this documentation|
|5/22/2020||Updated party block use cases|
In Subscription Parameters, removed the following:
|1/29/2020||Removed reference to TBA|
Key Events and Dates
For key events and dates please see the BrokerTec Integration time table.
Contact CME Group to get started with CME STP.
Testing and Certification
Certification using Autocert+ is required for all STP users.
Production Service Availability
CME STP service is available in PRODUCTION beginning 2 PM Central Time Sunday Afternoon, through 10 PM Central Time Friday. Internal testing could occur on weekends in the Production Environment (10 PM Friday – 2 PM Sunday Central Time).
Customers should only connect during the time of service availability.
Client System Impacts and Supporting Information
CME STP API Connectivity
Customers can connect to CME STP FIXML API via the following options:
New Release Connectivity (Internet Only)
To access CME STP API over the internet, customers must connect to the following URLs via HTTPS: https://servicesnr.cmegroup.com/cmestp/query
Clients must create a Domain Name Service (DNS) record in their systems to associate the DNS name and following IPs to access the STP services or they will receive certificate errors:
CME Glink, CME EConnect, CME LNet, CME Globex Hubs for Futures and Options
CME GLink, CME EConnect, CME Globex Hubs, CME Globex Hub – Aurora and CME LNet for BrokerTec on CME Globex
|CDN Leased lines and Site to Site VPN||https://services.cmegroup.com/cmestp/query||188.8.131.52|
Disaster Recovery Considerations
During a disaster recovery (DR) event clients will automatically be directed to the DR instance of CME STP. Clients do not need to make any connectivity changes.
Please find CME Group connectivity options here.
CME STP is built upon Representation State Transfer (REST) web service technology. In this methodology, HTTP URLs and methods (such as GET, POST, etc.), parameters, and statuses are used to model the remote procedure call behavior.
The API utilizes the industry standard FIXML format with custom CME extensions.
Mode of Connectivity
- Interaction with the API is session-less.
- Provide a username and password on each HTTP request and CME STP authenticates it.
- CME STP sends a token in response to valid subscription requests and valid query requests where the response requires multiple pages.
- Continue the subscription or request the next page of the query by sending CME STP this token on subsequent requests.
- Both customers and CME STP will use the
x-cme-tokencustom HTTP Request Header to transmit this token.
- Authentication is required in the header of the HTTP request and should be in format of “username:password” converted to base 64.
Subscriptions and Queries
Users requiring a continuous record of all trading activity may continue a subscription from one business day to the next. The user ceases sending HTTP requests and, on the next business day, continues the subscription with an HTTP request using the last token received on the previous day. This method ensures that the API will send the user any trading activity that occurred during the time period that the user made no HTTP requests. BrokerTec exchanges, security types, and input sources will be supported on the subscription.
Alternately, users may begin a new subscription each day, specifying a Start Time encompassing any time the user did not send HTTP requests following the end of the prior business day's subscription. Users should exercise caution with this method to ensure they do not miss trading activity by sending too narrow a time window, and that they do not process duplicate trades should the window overlap trades already received on the prior business day.
If the user begins a new subscription and does not send a Start Time, the subscription will begin at the present time and include no past trading activity. This method may result in missed trades should any trading occur after the user ceased sending HTTP requests on the prior business day and before the user initiated the new subscription.
Entitlement will not be available for instrument attributes and that customers may use the existing instrument attributes for filtering or filter on the client side.
CME STP supports data retrieval using subscriptions and queries:
- Queries return trade messages only up to the date and time that the query request was received by the API.
- Subscriptions continue to send trade messages to the user on an ongoing basis; there is no end date time.
Cash trades will be available from CME STP for 31 calendar days, based on the trade date. Repo trades and collateral allocations will be available from CME STP for 31 calendar days or the term of trade plus 7 calendar days, whichever is greater.
If a trade is corrected during this cycle, that trade will reflect the most recent information with a new transaction date and time.
Continuing a Subscription or Query
When responding to a successful Subscription Request, the API sends a token to the user so that the user may continue the subscription.
When responding to a successful Query Request, the API sends a token if the results of the query are incomplete (for example, more data is available).
- Upon receiving a successful response, submit a new Subscription request no sooner than three seconds later, which requires making another HTTP call that contains the token.
- For a Query, the user may make another HTTP call containing the token immediately
CME STP will only accept a subscription or query request without a token if it is a new subscription or query; all continuations of existing subscriptions or queries must include a token.
|API Input||API Output|
Subscription / Query Request: FIXML Trade Capture Report Request
Successful Subscription / Query Response: FIXML Trade Capture Report
Successful Subscription / Query Response: FIXML Collateral Report
|Subscription / Query Error Response: FIXML Trade Capture Report Request Ack|
API input messages continuing prior Subscription or Query Requests must send the token in the custom
x-cme-token HTTP header. API output messages will contain the token in the
x-cme-token HTTP header.
Each successful response from the API may return a different token. The user must send that new token in the next continued Subscription or Query Request.
Identifiers and Modes
The user must supply a unique identifier with each query in
/FIXML/TrdCaptRptReq/@ReqID which the API will echo back in
/FIXML/Batch/TrdCaptRpt/@ReqID for successful requests, and in
/FIXML/TrdCaptRptReqAck/@ReqID in case of errors. This enables the user to match the request with the resulting messages. When continuing a Subscription or a Request, the user may reuse the original
@ReqID or may send a new identifier. The API will respond with with the
@ReqID sent on the request.
The user must indicate in
/FIXML/TrdCaptRptReq/@SubReqTyp whether the message is a Subscription or a Query. The user must also indicate via
/FIXML/TrdCaptRptReq/@ReqTyp whether this is a new Subscription or Query, or a continuation of a prior Subscription or Query.
Subscription and Query Parameters
Use ONLY the following parameters to filter the query and / or subscription results. Omitting, changing, or adding filter criteria may cause undesired results. Every continuation of a Subscription or Query must contain all of the filter criteria of the original subscription or query. Times below, e.g. Start Time and End Time, use the XML
xs:dateTime syntax in ISO 8601 format. Time should be entered in UTC Timestamp format.
The following field indicates whether updates or collateral should be returned in request queries:
- IncludeCollateralIndicator (CollInd) - Can be set to No to prevent receipt of Collateral records.
Usage / Description
Party ID and Role
(e.g. Trading Firm, Asset Manager, Broker)
Multiple Parties allowed, and each Party ID must be in a separate Pty element.
|Clearing Business Date||Optional|
|Venue (Input Source)||Optional|
Values for BrokerTec:
|Product Type (e.g. FUT, OPT)||Optional|
Values for BrokerTec:
Values for BrokerTec:
|Secondary Trade ID||Optional|
|Client Order ID||Optional|
Optional on Requests
Required on Queries
Not Allowed on Requests
Optional on Queries
|Customers can enter an end time that is seconds before the Last Update Time (LastUpdateTm) timestamp on a revised trade (for example, a Give-up) to capture the trade in its original state.|
|Include Collateral Indicator|
|Indicates whether collateral should be returned in request result.|
Identifying BrokerTec Transactions
BrokerTec transactions will be distinguishable on the API by the Security Exchange and Security Type fields. The input source will distinguish between transactions on CME Globex, BrokerTec Direct, and externally registered deals.
General collateral (GC) repos require the post-trade allocation of specific bonds as collateral. To distinguish these collateral allocations from original trades, the API will support a new Collateral Report message.
Supporting Messages and Fields for BrokerTec Products
Collateral Allocations for General Collateral Repos
CME STP does not directly support allocating collateral for securities that support these BrokerTec General Collateral repos. This must be done through the CME GC Allocation API.
CME STP will support these allocations using the Collateral Report message.
Collateral allocation messages will be sent individually. Grouping and chaining will not be supported.
Trade and Allocation Identifiers
Existing CME Group Futures and Options trade and allocation identifiers will continue to be used.
Trade Capture Report Modifications
To harmonize BrokerTec and CME STP, the following fields and / or values will be supported:
- The Commission Group block will be used for commissions
- The Execution Timestamp will be included in the Report Side Block
A globally-unique identifier (GUID) will be included in the Secondary Trade ID field (TradeCaptureReport/@TrdID2) to guarantee a unique identifier across all business days and CME asset classes.
Fields that support futures and options trading will be present on the Trade Capture Report including: Multi-Leg Reporting Type, Trade Report Status, Venue Type, Client Order ID, and Execution ID.
General Collateral Repo Transactions
CME STP supports General Collateral (GC) repo transactions for the US and EU markets through the CME GC Allocation API with submission of collateral allocation transactions through the CME GC Allocation API.
After a GC repo trade has been completed, the Trade Capture Report and a shell Collateral Report record will be available in near real-time in STP. The Collateral Report and Trade Capture Report will have the same Secondary Trade ID (TrdID2).
Collateral Allocations are submitted using the CME GC Allocation API. Subsequent Collateral Reports will be available in near real-time in STP, and have the same TrdID2 as the Trade Capture Report and initial Collateral Report.
Identifiers for collateral allocations on the GC Allocation API will be common with STP identifiers.
Substitutions can be made for US GC transactions by submitting a Collateral Substitution using CME GC Allocation API. Subsequent Collateral Reports will be available in near real-time in STP, and have the same TrdID2 as the Trade Capture Report and initial Collateral Report.
- In STP the clearing organization is provided on the repo trades shell Collateral Report (Party Role = 21 and instrument reference) and the GC instrument is referenced on the allocations
All-or-None General Collateral Repo Trade Reconciliation
The All-or-None (AON) & None-AON Repo’s are distinct instruments with their own independent SecurityID’s & GUID’s on order entry and market data messaging.
- On MDP 3.0 a Repo AON-eligible instrument is identified in the Security Definition (tag 35-MsgType=d) message by tag
872=InstAttribValue bit 23=1 (All or None instrument). For related AON and parent instruments, the counterpart instrument is identified in the Security Definition
message repeating group tag 1650-RelatedSecurityID.
- In RD API v2 for Brokertec, the attribute relatedInstrumentGuidInt at the instrument level will identify relationship between AON & none-AON instruments
In CME STP, the TradeCaptureReport for AON Repo reflects the Non-AON instrument SecurityID & GUID.
GC Repo Trade example
- A None-AON GC Repo trade was executed on Instrument 11111.
- TradeCaptureReport (AE) with SecondaryTradeID (1040) = 1234 is sent along with GC Shell (BA).
- A related AON Repo trade was executed on Instrument 99999.
- TradeCaptureReport (AE) with SecondaryTradeID (1040) = abcd reported as None-AON GC Repo instrument 11111 along with a GeneralCollateral Shell (BA)
GC API trade search (/trades/search) result will reflect both of the None-AON and AON trades while CME STP will only reflect the Non-AON instrument details.
To reconcile GC API trade records with CME STP TradeCaptureReport (AE) customers are expected to use the Related Instrument attributes for AON Repo to identify the None-AON Repo.
CME STP Message Specifications and Workflows
- CME STP FIXML - Message Specifications for BrokerTec Trades
- CME STP - Samples for BrokerTec Trades
- CME STP FIXML - Message Flows for BrokerTec Trades
For technical development support, contact Certification Support for Electronic Trading (CSET).
For production requests, please contact the Global Command Center (GCC).
For all other inquiries, please contact Global Account Management (GAM).
All information contained herein (“Information”) is for informational purposes only and is the intellectual property of CME Group Inc. or one of its subsidiaries (together, “CME”), including NEX Group Ltd (“NEX”) or third parties. Access to the Information by anyone other than the intended recipient is unauthorised and any disclosure, copying or redistribution is prohibited without CME’s prior written approval. In no circumstances will CME be liable for any indirect or direct loss, or consequential loss or damages including without limitation, loss of business or profits arising from the use of, any inability to use, or any inaccuracy in the Information. NEX is a private limited company registered in England and Wales under number 10013770 and certain of its affiliates are authorised and regulated by regulatory authorities. All Information contained herein is subject to change and subject to applicable regulatory approvals. NEX subsidiaries that are regulated by the UK Financial Conduct Authority ("FCA") are required to retain records of telephone conversations and other electronic communications for a period of 5 years (7 years at the request of the FCA), copies of which are available on request (which may be subject to a fee). BrokerTec Americas LLC is a registered broker-dealer with the U.S. Securities and Exchange Commission, is a member of the Financial Industry Regulatory Authority, Inc. (www.FINRA.org), and is a member of the Securities Investor Protection Corporation (www.SIPC.org). For further regulatory information please see
US Treasury Off the Run securities are offered by ICAP Securities USA LLC.
Futures trading is not suitable for all investors, and involves the risk of loss. Futures are a leveraged investment, and because only a percentage of contract value is required to trade, it is possible to lose more than the amount of money deposited for a futures position. Therefore, traders should only use funds that they can afford to lose without affecting their lifestyles. And only a portion of those funds should be devoted to any one trade because they cannot expect to profit on every trade.
All references to options refer to options on futures.
CME Group is a trademark of CME Group Inc. The Globe Logo, CME, Chicago Mercantile Exchange, Globex, iLink, E-mini, CME EOS Trader, Galax-C, FirmSoft, CME DataSuite, and CME DataMine are trademarks of Chicago Mercantile Exchange Inc. New York Mercantile Exchange, NYMEX, miNY, and ClearPort are registered trademarks of the New York Mercantile Exchange, Inc. COMEX is a trademark of Commodity Exchange, Inc.
FIX™ and FAST™ are trademarks of FIX Protocol Limited. FIX/FASTsm is a service mark of FIX Protocol Limited.
Dow Jonessm, Dow Jones AIG Commodity Indexsm, The Dowsm, Dow Jones Industrial Averagesm, and DJIAsm are service marks of Dow Jones & Company, Inc. and American International Group, Inc. (AIG) and have been licensed for use for certain purposes by the Board of Trade of the City of Chicago, Inc (CBOT®). CBOT futures and options on futures contracts based on the Dow Jones Industrial Averagesm are not sponsored, endorsed, sold or promoted by Dow Jonessm, and Dow Jonessm makes no representation regarding the advisability of trading such product(s).
BM&FBOVESPA™ is a trademark of BM&FBOVESPA, KRX™ is a trademark of Korea Exchange, DME™ is a trademark of Dubai Mercantile Exchange, BMD™ is a trademark of Bursa Malaysia, BMV™ is a trademark of Bolsa Mexicana De Valores.
Standard & Poor’s, S&P®, S&P 500®, S&P-GSCI™, S&P-GSCI Spot Index™, S&P-GSCI Excess Return Index™, S&P-GSCI Total Return Index™, S&P-GSCI Non-Energy Excess Return Index™, S&P-GSCI Light Energy Excess Return Index™, S&P-GSCI Livestock Excess Return Index™, S&P-GSCI Industrial Metals Excess Return Index™, S&P-GSCI Energy Excess Return Index™, S&P-GSCI WTI Oil Excess Return Index™, S&P-GSCI Natural Gas Excess Return Index™, S&P-GSCI Grains Excess Return Index™, S&P-GSCI Agricultural Excess Return Index™, Standard & Poor’s®, Standard & Poor’s 500™, 500™, S&P 100®, Standard & Poor’s 100™, S&P MidCap 400™ Index, S&P SmallCap 600™ Index, S&P 500/CITIGROUP Growth Index™, S&P 500/CITIGROUP Value Index™, Standard & Poor’s 500/CITIGROUP Value Index™, S&P Energy Stock Price Index™, Standard & Poor’s Energy Stock Price Index™, Standard & Poor’s Financial Stock Price Index™, S&P High Technology Stock Price Index™, Standard & Poor’s High Technology Stock Price Index™, S&P Public Utility Stock Price Index™, Standard & Poor’s Public Utility Stock Price Index™, S&P Consumer Staple Stock Price Index™, Standard & Poor’s Consumer Staple Stock Price Index™, S&P Transportation Stock Index™, Standard & Poor’s Transportation Stock Price Index™, S&P Euro Index™, S&P Euro Plus Index™, S&P 500 GICS Sector Indices™, SPDR®, Standard & Poor’s Depositary Receipts™, S&P Asia™, Bxy Trakrs™ are trademarks of The McGraw-Hill Companies, Inc. and have been licensed for use by Chicago Mercantile Exchange Inc.
Eris Exchange and the Eris Logo are registered trademarks of Eris Exchange, LLC. Eris SwapBook, Eris BlockBox, and Eris PAI are trademarks of Eris Exchange, LLC.
All other trademarks are the property of their respective owners.
The information within this site has been compiled by CME Group for general purposes only. CME Group assumes no responsibility for any errors or omissions. Additionally, all examples in this brochure are hypothetical situations, used for explanation purposes only, and should not be considered investment advice or the results of actual market experience.
All matters pertaining to rules and specifications herein are made subject to and are superseded by official CME, CBOT, and NYMEX rules. Current rules should be consulted in all cases concerning contract specifications.
Copyright © 2019 CME Group Inc. All rights reserved.