BCU Bank · OAuth Scopes

BCU Bank OAuth Scopes

OAuth 2.0 searched

BCU 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 BCU 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 Data RightConsumer BankingMutual BankAustralia
Scopes: 5 Flows: authorizationCode Method: searched

Scopes (5)

ScopeDescriptionFlows
bank:accounts.basic:read Read basic account information (account list, product category, masked account number, balances).
bank:accounts.detail:read Read detailed account information including features, fees, terms and account-holder details.
bank:transactions:read Read account transactions and transaction detail.
bank:regular_payments:read Read regular payments - 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/bcu-bank-cds-banking-products-openapi.yml (per-operation x-scopes)
docs: https://consumerdatastandardsaustralia.github.io/standards/#authorisation-scopes
notes: >-
  The CDS Banking OpenAPI declares no components.securitySchemes, so the OAuth
  scope surface is derived from the per-operation x-scopes extension in the spec
  and enriched from the DSB Consumer Data Standards authorisation-scopes
  reference. These are the standardised CDR banking data-cluster scopes granted
  through the CDR consent flow to Accredited Data Recipients. The Product
  Reference Data endpoints (listBankingProducts, getBankingProductDetail) are
  public and require no scope.
schemes:
- name: OAuth2 (CDR authorization-code + PKCE, FAPI 1.0 Advanced)
  source: DSB Consumer Data Standards Security Profile
  flows:
  - flow: authorizationCode
scopes:
- scope: bank:accounts.basic:read
  description: Read basic account information (account list, product category, masked account number, balances).
  operations:
  - listBankingAccounts
  - listBankingBalancesBulk
  - listBankingBalancesSpecificAccounts
  - getBankingBalance
- scope: bank:accounts.detail:read
  description: Read detailed account information including features, fees, terms and account-holder details.
  operations:
  - getBankingAccountDetail
- scope: bank:transactions:read
  description: Read account transactions and transaction detail.
  operations:
  - listBankingTransactions
  - getBankingTransactionDetail
- scope: bank:regular_payments:read
  description: Read regular payments - 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

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