CME Group · OAuth Scopes

CME Group OAuth Scopes

OAuth 2.0 searched

CME Group publishes 5 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the CME Group API on a user’s behalf.

Tokens are issued from https://auth.cmegroup.com/as/token.oauth2.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Capital MarketsDerivativesExchangeFinancial MarketsFuturesMarket DataOptionsReference DataTradingFortune 1000

Scopes: 5 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://auth.cmegroup.com/as/token.oauth2 https://authnr.cmegroup.com/as/token.oauth2

Flows
clientCredentials

Scopes (5)

Scope	Description	Flows
UNOEntitlement	CME Group entitlement scope advertised by the authorization server (RFC 8414 scopes_supported).	clientCredentials
openid	OpenID Connect authentication scope.	authorizationCode
profile	OpenID Connect profile claims.	authorizationCode
email	OpenID Connect email claim.	authorizationCode
offline_access	Refresh-token issuance for long-lived access.	authorizationCode

📄 Provider scope reference: https://cmegroupclientsite.atlassian.net/wiki/spaces/EPICSANDBOX/pages/457316022/Client+API+Service+Adoption+Using+OAuth+2.0+Protocol

Source

OAuth Scopes

generated: '2026-07-22'
method: searched
source: https://auth.cmegroup.com/.well-known/oauth-authorization-server
docs: https://cmegroupclientsite.atlassian.net/wiki/spaces/EPICSANDBOX/pages/457316022/Client+API+Service+Adoption+Using+OAuth+2.0+Protocol
notes: >-
  CME Group authorization is primarily entitlement-based (per-API-ID
  entitlements managed in the CME Customer Center), not scope-based. The
  PingFederate authorization server at auth.cmegroup.com advertises the scopes
  below in its anonymous RFC 8414 metadata; API access itself is granted by
  entitling the OAuth API ID to each API rather than by requesting granular
  scopes. No public OpenAPI declares oauth2 scopes.
schemes:
  - name: CMEGroupOAuth
    source: well-known/cme-group-oauth-authorization-server.json
    flows:
      - flow: clientCredentials
        tokenUrl: https://auth.cmegroup.com/as/token.oauth2
      - flow: clientCredentials
        tokenUrl: https://authnr.cmegroup.com/as/token.oauth2
scopes:
  - scope: UNOEntitlement
    description: CME Group entitlement scope advertised by the authorization server (RFC 8414 scopes_supported).
    flows: [clientCredentials]
    sources: [well-known/cme-group-oauth-authorization-server.json]
  - scope: openid
    description: OpenID Connect authentication scope.
    flows: [authorizationCode]
    sources: [well-known/cme-group-openid-configuration.json]
  - scope: profile
    description: OpenID Connect profile claims.
    flows: [authorizationCode]
    sources: [well-known/cme-group-openid-configuration.json]
  - scope: email
    description: OpenID Connect email claim.
    flows: [authorizationCode]
    sources: [well-known/cme-group-openid-configuration.json]
  - scope: offline_access
    description: Refresh-token issuance for long-lived access.
    flows: [authorizationCode]
    sources: [well-known/cme-group-openid-configuration.json]