Police Bank · OAuth Scopes
Police Bank OAuth Scopes
OAuth 2.0
derived
Police 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 Police 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: derived
Scopes (5)
| Scope | Description | Flows |
|---|---|---|
| bank:accounts.basic:read | Basic account information - the list of a member's accounts plus balances. | authorizationCode |
| bank:accounts.detail:read | Detailed account information - account numbers, features, fees, rates and other account detail beyond the basic list. | authorizationCode |
| bank:transactions:read | Transactions - the ability to read a member's transactions for authorised accounts, including transaction detail. | authorizationCode |
| bank:regular_payments:read | Regular payments - direct debits, scheduled payments and instalment plans configured on a member's accounts. | authorizationCode |
| bank:payees:read | Saved payees - the member's stored domestic, international and BPAY payees. | authorizationCode |
📄 Provider scope reference: https://consumerdatastandardsaustralia.github.io/standards/#authorisation-scopes