CME Globex Order Entry Web Service APIs

Clients now have access to CME Group futures and options on the new Order Entry suite of APIs - Hosted by Google Cloud. This solution is accessible over the public internet without the commitment of leased line or colocation investments. RESTful and WebSocket APIs with full order routing and instrument creation functionality deliver real-time trading and market access. This lightweight product is optimized for the needs of less latency sensitive traders and algorithms, while still offering fulsome functionality and utilizing the full suite of CME Globex risk and credit controls.

The OE APIs are made up of two Web Service APIs; RESTful and WebSocket. These APIs support:

• Order Submission and Modifications

• Spread Creation (UDS) and Request for Quotes (RFQ) Capabilities

• Order and Trade information

Contents

Revision History

Key Events and Dates

Testing and Certification

Customers are required to certify in New Release before accessing the APIs in Production. 

Contact Global Account Management (GAM) for more information on certification.

Contact Certification Support for Electronic Trading (CSET) for assistance with testing and certification. 

Onboarding and Entitlements

Client Onboarding

Authorization and Entitlement

A registered OAuth API ID is required to access the CME OE API services. API IDs for CME Group Logins are created and managed in the CME Customer Center - My Profile menu. Client API IDs must also be entitled prior to accessing CME OE APIs.

Complete the step(s) that are applicable to your account:

Entitlements and Roles

To request entitlements be added to the API IDs, contact Global Account Management (GAM) requesting role assignments to New Release and Production API IDs.

All OE API IDs must have a specific role assigned:

• CME Globex Order Submitter

  • Can submit orders

  • Can request order status

• CME Globex Order Viewer

  • Can request order and trade status

Product and Instrument Referential Data

OE API does not support instrument referential data or market data. Clients must obtain instrument referential data, and market data if desired, from one of the many other services offered by CME Group:

• Referential Data APIs

•  

  • Reference Data API

  • Reference Data Warehouse on Google Cloud

• Market Data APIs

•  

  • Market Data Platform

  • Market Data Over WebSocket API

  • CME SmartStream on Google Cloud

OWASP Compliance

The OE APIs are hosted on Google Cloud and protected by Google Cloud Armor with preconfigured Web Application Firewall(WAF) rules leveraging the OWASP Top 10 rules.

Customers must test their applications' compliance with the OWASP Top 10 rules in the New Release environment to ensure no Production issues occur.

Access CME OE APIs on Google Cloud

To access the CME OE API Web Services  in the New Release and Production environments, an OAuth API ID and access token are required.

OAuth 2.0 Authorization Server Access Token Retrieval Endpoints

The below Endpoints are available to request and refresh access tokens in the New Release and Production environments.     

Connectivity Methods

Once clients have completed onboarding and granted entitlements they can access the OE APIs.  OE APIs support the following API protocols:

• OE API supports HTTPS RESTful connections over the internet. 

• WebSocket API supports WSS connections over the internet.

Base URL for OE APIs

HTTPS RESTful API

• The value from the Path column with environment specific Base URL prefix will be a specific end point for the HTTPS call.

• Each HTTPS call must have the header parameter "Authorization" with value "Bearer" pre-pended to the OAuth token (including a space separator).
  example: "Bearer <Oauth Access token>"

Web Socket API

• Web Socket Initiation must have the header parameter "Authorization" with value "Bearer" pre-pended to the OAuth token (including a space separator).
  example: "Bearer <Oauth Access token>"

Message Specifications

The business message specifications for CME OE APIs are available at Order Entry API V2

Technical Considerations

• WebSocket inbound messages contain sequence numbers. If a gap is detected, customers should disconnect and reconnect. Once reconnected a order status or trade search message should be sent.

• WebSocket customers will receive heartbeats from Order Entry Service every 5 seconds to ensure connectivity.

• Clients on the WebSocket API should receive a message at least once every 5 seconds. If you have not received any message for 15 seconds, please disconnect and re-connect to ensure a stable instance. Clients can use Order Status and Trade Search to recover any possible missed information.

Cancel on Disconnect

• Only available for WebSocket connections.

• Cancel on Disconnect capability must be established during WebSocket initialization request.

• Upon ungraceful disconnect, (non GT) resting orders for registered ExecutionFirmID, AccountID and OperatorID will be removed from the book.

Fill and Kill (FAK) and Fill or Kill (FOK) Order Duration Types

When FOK order duration type is sent, customers should be aware of the response. Customers will receive an order status with duration type Fill and Kill (FAK) and minimum quantity integer equal to total order quantity.

• FOK orders must be fully filled immediately, or the entire order is canceled with an order status of expired.

• FAK orders are immediately executed against resting orders. If the order cannot be fully filled, the remaining balance is canceled with an order status of expired. A minimum quantity can be specified. If the specified minimum quantity cannot be filled, the order is cancelled with a status of expired.

Stop Orders

When Stop orders (with protection) are sent, customers should be aware of the response:

• Customer submits a New Order message with order type as STOP with stop price.

• When a Stop order (with protection) order is accepted, a message is returned with type as STOP LIMIT.

Post-Trade Instructions 

More information on Post-Trade Instructions will be available soon.

Special Character Restrictions

OE APIs support alphanumeric characters in the Customer Order Id and Customer Account Id fields with a specific number of allowable special characters.

• Operator ID - This value represents the individual or team submitting the message and is subject to registration requirements and character limits as required by CME Group -Rule-576  Advisory.

• Customer Account ID -  A unique account identifier in Execution Firm accounts.

Request Throttles 

Order Management, User-Defined Instrument and Query Status services are throttled as follows:

• The Order Entry and User-Defined Instrument APIs are limited to 8 post per second for each API. 

• The Order Query Status API is limited to 8 total concurrent requests.

• Any call that exceeds these limits will result in a Response Code 429 (rate limit has been exhausted) .

Sample messages

RESTful WebSerivce

Crude Oil futures LIMIT order submitted for a quantity of 4 at a price of 2025

WebSocket

Crude Oil futures LIMIT order submitted for a quantity of 4 at a price of 2025

Includes Heartbeat messages with sequence numbers

Related Content

Partner Exchange Impacts

Order management is not allowed for the following Partner Exchanges:

Only CME Group futures and options on CME Globex are available via the OE APIs. Partner Exchange markets, BrokerTec and EBS Markets, and trade submissions are not supported.

Contact Information

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

For production requests, technical assistance and order status, please contact the Global Command Center (GCC). 

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