Defence Bank · OAuth Scopes

Defence Bank OAuth Scopes

OAuth 2.0 searched

Defence 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 Defence Bank 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.

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

Scopes (5)

ScopeDescriptionFlows
bank:accounts.basic:read Read basic account information (account list, basic account detail).
bank:accounts.detail:read Read detailed account information (account terms, features, and identifiers).
bank:transactions:read Read account transactions and transaction detail.
bank:regular_payments:read Read direct debits, scheduled payments, and instalment plans.
bank:payees:read Read saved payees.

Source

OAuth Scopes

Raw ↑
generated: '2026-07-20'
method: searched
source: openapi/defence-bank-cds-banking-products-openapi.yml (x-scopes per operation)
docs: https://consumerdatastandardsaustralia.github.io/standards/#authorisation-scopes
description: >-
  CDR authorization scopes govern the authenticated consumer-data-sharing endpoints.
  They are captured from the per-operation x-scopes extension in the OpenAPI plus the
  Consumer Data Standards authorisation-scopes reference. The public Product Reference
  Data endpoints require no scope (unauthenticated). Scopes are granted by the consumer
  during CDR consent to an Accredited Data Recipient.
schemes:
- name: CDR-FAPI-OAuth2
  source: Consumer Data Standards security profile
  flows:
  - flow: authorizationCode
    profile: FAPI / OIDC hybrid
scopes:
- scope: bank:accounts.basic:read
  description: Read basic account information (account list, basic account detail).
  operations: [listBankingAccounts, getBankingAccountDetail, listBankingBalancesBulk, listBankingBalancesSpecificAccounts, getBankingBalance]
- scope: bank:accounts.detail:read
  description: Read detailed account information (account terms, features, and identifiers).
  operations: [getBankingAccountDetail]
- scope: bank:transactions:read
  description: Read account transactions and transaction detail.
  operations: [listBankingTransactions, getBankingTransactionDetail]
- scope: bank:regular_payments:read
  description: Read direct debits, scheduled payments, and instalment plans.
  operations: [listDirectDebits, listDirectDebitsBulk, listDirectDebitsSpecificAccounts, listScheduledPayments, listScheduledPaymentsBulk, listScheduledPaymentsSpecificAccounts, listInstalmentPlans, listInstalmentPlansBulk]
- scope: bank:payees:read
  description: Read saved payees.
  operations: [listBankingPayees, getBankingPayeeDetail]
notes:
  - Product Reference Data endpoints (listBankingProducts, getBankingProductDetail) are public and require no scope.
  - CDR also defines the openid and (via the register) profile scopes for the OIDC layer; the bank:* scopes above are the data-cluster scopes declared in this spec.

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/defence-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.