CME Globex Order Entry Web Service APIs
...
OAuth 2.0 Authorization Server Endpoints | ||
---|---|---|
Detail | New Release | Production |
OAuth Token Endpoint | https://authnr.cmegroup.com/as/token.oauth2 | https://auth.cmegroup.com/as/token.oauth2 |
Info |
---|
Tokens will expire after 30 minutes. |
Connectivity Methods
Once clients have completed onboarding and granted entitlements they can access the OE APIs. OE APIs support the following API protocols:
...
Environment | Base URL |
---|---|
New Release | https://markets.api.uat.cmegroup.com/orderentry/v2 |
Production | https://markets.api.cmegroup.com/orderentry/v2 |
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>"
Environment | Base URL |
---|---|
AutoCert+ Certification | wss://markets.api.uat.cmegroup.com/autocert/orderentry |
New Release | wss://markets.api.uat.cmegroup.com/orderentry/v2 |
Production | wss://markets.api.cmegroup.com/orderentry/v2 |
...
- 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.
...