CME Group OAuth Scopes
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.
OAuth endpoints
https://auth.cmegroup.com/as/token.oauth2 https://authnr.cmegroup.com/as/token.oauth2
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 |
| 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
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for oauth scopes
4 MCP tools reach this
find_scopesBrowse and filter every scope set in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/scopes/cme-group-scopes"
curl "https://apis.io/api/v1/scopes?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.