Unity Bank · OAuth Scopes

Unity Bank OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from discovered-via-cdr-register.

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.

FinancialBanksOpen BankingCDRConsumer Data RightConsumer BankingAustraliaMutual BankProduct Reference Data
Scopes: 5 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
discovered-via-cdr-register
Token URL
discovered-via-cdr-register
Flows
authorizationCode

Scopes (5)

ScopeDescriptionFlows
bank:accounts.basic:read Read basic account information - account name, type, balance and masked account number - for accounts the member has consented to share. authorizationCode
bank:accounts.detail:read Read detailed account information - full account numbers, features, fees, deposit/lending rates, address and other account detail - for consented accounts. authorizationCode
bank:transactions:read Read transactions for consented accounts, with date, amount and text filtering. authorizationCode
bank:payees:read Read the member's saved payees (name, type, and payee detail) for consented data. authorizationCode
bank:regular_payments:read Read regular payment arrangements - direct debits and scheduled/recurring payments - for consented accounts. authorizationCode

Source

OAuth Scopes

Raw ↑
generated: '2026-07-21'
method: searched
source: openapi/unity-bank-cds-banking-products-openapi.yml (x-scopes)
docs: https://consumerdatastandardsaustralia.github.io/standards/#authorisation-scopes
notes: >-
  Unity Bank is a CDR data holder. The public Product Reference Data surface is
  unauthenticated, but the broader consumer-authorized CDR Banking surface
  (Accounts, Balances, Transactions, Payees, Direct Debits & Scheduled Payments)
  is protected by the CDR OIDC/FAPI 2.0 authorization model. The scopes below are
  the standard DSB Consumer Data Right banking authorisation scopes carried as
  x-scopes on the operations in the harvested shared CDR Banking API (v1.36.0) and
  enriched from the published Consumer Data Standards authorisation-scopes
  reference. Authorization and token endpoints are not fixed URLs: an Accredited
  Data Recipient discovers the data holder's OIDC configuration dynamically via the
  CDR Register, then completes a PAR + mTLS / private_key_jwt FAPI authorization
  flow after member consent. No public authorization-server metadata is exposed
  (well-known probe returned 404, as expected for a data holder behind the Register).
schemes:
- name: CDR-OIDC-FAPI
  type: oauth2
  profile: FAPI 2.0 (CDR Security Profile)
  source: openapi/unity-bank-cds-banking-products-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: discovered-via-cdr-register
    tokenUrl: discovered-via-cdr-register
    par: true
    client_auth: [mtls, private_key_jwt]
    consent: member-authorized
scopes:
- scope: bank:accounts.basic:read
  description: >-
    Read basic account information - account name, type, balance and masked
    account number - for accounts the member has consented to share.
  flows: [authorizationCode]
  operations: [listBankingAccounts, getBankingBalance, listBankingBalancesBulk, listBankingBalancesSpecificAccounts]
  sources: [openapi/unity-bank-cds-banking-products-openapi.yml]
- scope: bank:accounts.detail:read
  description: >-
    Read detailed account information - full account numbers, features, fees,
    deposit/lending rates, address and other account detail - for consented accounts.
  flows: [authorizationCode]
  operations: [getBankingAccountDetail]
  sources: [openapi/unity-bank-cds-banking-products-openapi.yml]
- scope: bank:transactions:read
  description: >-
    Read transactions for consented accounts, with date, amount and text filtering.
  flows: [authorizationCode]
  operations: [listBankingTransactions, getBankingTransactionDetail]
  sources: [openapi/unity-bank-cds-banking-products-openapi.yml]
- scope: bank:payees:read
  description: >-
    Read the member's saved payees (name, type, and payee detail) for consented data.
  flows: [authorizationCode]
  operations: [listBankingPayees, getBankingPayeeDetail]
  sources: [openapi/unity-bank-cds-banking-products-openapi.yml]
- scope: bank:regular_payments:read
  description: >-
    Read regular payment arrangements - direct debits and scheduled/recurring
    payments - for consented accounts.
  flows: [authorizationCode]
  operations: [listDirectDebits, listDirectDebitsBulk, listDirectDebitsSpecificAccounts, listScheduledPayments, listScheduledPaymentsBulk, listScheduledPaymentsSpecificAccounts]
  sources: [openapi/unity-bank-cds-banking-products-openapi.yml]

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/unity-bank-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.

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