Azupay · OAuth Scopes

Azupay OAuth Scopes

OAuth 2.0 searched

Azupay publishes 1 OAuth 2.0 scope. Scopes are the fine-grained permissions an application requests at authorization time to act against the Azupay API on a user’s behalf.

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.

PaymentsAustraliaReal-Time PaymentsAccount-to-AccountNew Payments PlatformPayIDPayToMoney TransferConfirmation of PayeeOpen Banking
Scopes: 1 Flows: Method: searched

Scopes (1)

ScopeDescriptionFlows
oauth2AllowedScopes Per-client scope set enabling access to the specific Azupay REST endpoints agreed for the integration; exact scope names are provisioned and returned by Azupay, not published publicly. clientCredentials

Source

OAuth Scopes

Raw ↑
generated: '2026-07-24'
method: searched
source: openapi/*.yml (no oauth2 in spec)
docs: https://developer.azupay.com.au/docs/oauth-20-api
note: The REST OpenAPI declares only apiKey security. Docs document OAuth 2.0 client-credentials as an
  additional server-to-server option; the permitted scope set (oauth2AllowedScopes) is provisioned per
  client by Azupay and returned by the OAuth 2.0 connection-details endpoint (getClientOAuth2 / enableClientOAuth2)
  rather than published as a fixed public catalogue.
schemes:
- name: OAuth2ClientCredentials
  flow: clientCredentials
  tokenUrl: dynamic — returned as oauth2TokenUrl by POST /client/{clientId}/oauth2 (enableClientOAuth2)
  grantType: client_credentials
  tokenType: JWT bearer
  ttl: oauth2TtlInSecs (short-lived; token response carries expires_in)
scopes:
- scope: oauth2AllowedScopes
  description: Per-client scope set enabling access to the specific Azupay REST endpoints agreed for the
    integration; exact scope names are provisioned and returned by Azupay, not published publicly.
  flows:
  - clientCredentials