Discover · OAuth Scopes

Discover OAuth Scopes

OAuth 2.0 searched

Discover publishes 8 OAuth 2.0 scopes via the clientCredentials and authorizationCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Discover API on a user’s behalf.

Tokens are issued from https://apis.discover.com/auth/oauth/v2/token.

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.

Credit CardsPaymentsCard NetworkTokenizationFinancial ServicesFraudFortune 500

Scopes: 8 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://identity.discoverglobalnetwork.com/oauth2/default/v1/authorize

Token URL
https://apis.discover.com/auth/oauth/v2/token https://identity.discoverglobalnetwork.com/oauth2/default/v1/token

Flows
clientCredentialsauthorizationCode

Scopes (8)

Scope	Description	Flows
openid	OIDC authentication of the portal user	authorizationCode
profile	Portal user profile claims	authorizationCode
email	Portal user email claim	authorizationCode
address	Portal user address claim	authorizationCode
phone	Portal user phone claim	authorizationCode
offline_access	Refresh-token issuance for the portal session	authorizationCode
device_sso	Okta device single sign-on	authorizationCode
interclient_access	Okta inter-client token exchange	authorizationCode

📄 Provider scope reference: https://partner.discoverglobalnetwork.com/going-live-with-discover?tab=developer-guide

Source

OAuth Scopes

generated: '2026-09-06'
method: searched
source: https://partner.discoverglobalnetwork.com/going-live-with-discover?tab=developer-guide
docs: https://partner.discoverglobalnetwork.com/going-live-with-discover?tab=developer-guide
note: >-
  Discover documents an OAuth 2.0 client-credentials scope model but does NOT publish a scope
  catalogue. Section 2.1 of the developer guide states scopes are "provided in the Discover
  Developer Center upon review by Discover" and the request form is literally
  scope=DISCOVER_SCOPE_NAME - a placeholder. The concrete scope names are issued per partner, per
  API product and per environment behind the invitation-only Developer Center login, so no scope
  list is recorded here. The published scopes below belong to the Okta authorization server that
  signs humans into the partner portal, not to the API gateway.
schemes:
- name: DiscoverApiGatewayOAuth2
  source: https://partner.discoverglobalnetwork.com/going-live-with-discover?tab=developer-guide
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.discover.com/auth/oauth/v2/token
    scopes_published: false
    scope_parameter: scope=<DISCOVER_SCOPE_NAME>
    permission_model: 'read, write and delete access levels granted per API resource'
- name: DiscoverPartnerPortalOkta
  source: well-known/discover-identity-default-openid-configuration.json
  probed: '2026-09-06'
  audience: human sign-in to the Discover Partner Product Portal / Developer Center
  flows:
  - flow: authorizationCode
    issuer: https://identity.discoverglobalnetwork.com/oauth2/default
    authorizationUrl: https://identity.discoverglobalnetwork.com/oauth2/default/v1/authorize
    tokenUrl: https://identity.discoverglobalnetwork.com/oauth2/default/v1/token
    revocationUrl: https://identity.discoverglobalnetwork.com/oauth2/default/v1/revoke
    introspectionUrl: https://identity.discoverglobalnetwork.com/oauth2/default/v1/introspect
scopes:
- scope: openid
  description: OIDC authentication of the portal user
  flows: [authorizationCode]
  sources: [well-known/discover-identity-default-openid-configuration.json]
- scope: profile
  description: Portal user profile claims
  flows: [authorizationCode]
  sources: [well-known/discover-identity-default-openid-configuration.json]
- scope: email
  description: Portal user email claim
  flows: [authorizationCode]
  sources: [well-known/discover-identity-default-openid-configuration.json]
- scope: address
  description: Portal user address claim
  flows: [authorizationCode]
  sources: [well-known/discover-identity-default-openid-configuration.json]
- scope: phone
  description: Portal user phone claim
  flows: [authorizationCode]
  sources: [well-known/discover-identity-default-openid-configuration.json]
- scope: offline_access
  description: Refresh-token issuance for the portal session
  flows: [authorizationCode]
  sources: [well-known/discover-identity-default-openid-configuration.json]
- scope: device_sso
  description: Okta device single sign-on
  flows: [authorizationCode]
  sources: [well-known/discover-identity-default-openid-configuration.json]
- scope: interclient_access
  description: Okta inter-client token exchange
  flows: [authorizationCode]
  sources: [well-known/discover-identity-default-openid-configuration.json]
gaps:
- id: api-scope-catalogue-unpublished
  detail: >-
    No public list of the DISCOVER_SCOPE_NAME values a partner can request. A prospective
    integrator cannot see, before signing, what authorization granularity each API product offers.

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.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/discover-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.