generated: '2026-07-24'
method: searched
source: https://cardsapidocs.thredd.com/docs/get-an-authentication-token
docs: https://cardsapidocs.thredd.com/v2.0/docs/get-an-authentication-token
note: >-
  Thredd uses OAuth2 client-credentials; the access-token audience/scope claims
  select the backing platform services. Scopes are provisioned per client by the
  Implementation Manager (not requested via a scope parameter in the token call).
  The scope set below is taken verbatim from the documented example access-token
  claims (aud + scope arrays).
schemes:
  - name: oauth2ClientCredentials
    flow: clientCredentials
    token_url: https://oauthuat.globalprocessing.net/connect/token
scopes:
  - scope: coreapi
    description: Core issuing and card-management platform API (Cards API Hub core).
    flows: [clientCredentials]
  - scope: claimsapi
    description: Claims / disputes and chargeback platform service.
    flows: [clientCredentials]
  - scope: ctslite
    description: Card Transaction System (CTS) transaction data and reporting service.
    flows: [clientCredentials]
  - scope: dalapi
    description: Data access layer service.
    flows: [clientCredentials]
  - scope: mdesrttapi
    description: Mastercard Digital Enablement Service (MDES) real-time tokenisation service for digital wallets.
    flows: [clientCredentials]
  - scope: relayapi
    description: Relay / event-relay service supporting webhooks and notifications.
    flows: [clientCredentials]