Regional Australia Bank · Authentication Profile

Regional Australia Bank Authentication

Authentication

Regional Australia Bank secures its APIs with none, oauth2, and openIdConnect across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

FinancialBanksOpen BankingCDRConsumer BankingAustraliaCustomer OwnedProduct Reference DataMutual Bank
Methods: none, oauth2, openIdConnect Schemes: 3 OAuth flows: authorizationCode API key in:

Security Schemes

PublicPRD none
CDR-OAuth2 oauth2
scheme: authorizationCode
CDR-OIDC openIdConnect

Source

Authentication Profile

Raw ↑
generated: '2026-07-20'
method: derived
source: openapi/regional-australia-bank-cds-banking-products-openapi.yml
docs: https://consumerdatastandardsaustralia.github.io/standards/#security-profile
note: >-
  Two distinct surfaces. (1) The public Product Reference Data (PRD) API
  (Get Products / Get Product Detail) is PUBLIC and UNAUTHENTICATED - no API key,
  no token; only the required `x-v` version header. (2) The authenticated CDR
  consumer data sharing operations use the CDR security profile: OAuth2
  Authorization Code with PKCE, OpenID Connect, and FAPI-aligned protections
  (mutual-TLS sender-constrained tokens, request objects, PAR). Access is limited
  to accredited data recipients on the CDR Register. The harvested CDS spec does
  not declare formal `components.securitySchemes`; it carries the required scopes
  as `x-scopes` extensions per operation.
summary:
  types: [none, oauth2, openIdConnect]
  public_surface: unauthenticated
  oauth2_flows: [authorizationCode]
  oauth2_profile: CDR security profile (FAPI 1.0 Advanced-aligned)
schemes:
  - name: PublicPRD
    type: none
    description: >-
      Public Product Reference Data endpoints require no authentication. The only
      mandatory request header is `x-v` (endpoint version). Applies to
      listBankingProducts and getBankingProductDetail.
    sources: [openapi/regional-australia-bank-cds-banking-products-openapi.yml]
  - name: CDR-OAuth2
    type: oauth2
    scheme: authorizationCode
    description: >-
      OAuth2 Authorization Code with PKCE for consumer data sharing; scopes are
      the CDR banking scopes (bank:accounts.basic:read, bank:accounts.detail:read,
      bank:transactions:read, bank:regular_payments:read, bank:payees:read).
    scopes_artifact: scopes/regional-australia-bank-scopes.yml
    sources: [openapi/regional-australia-bank-cds-banking-products-openapi.yml]
  - name: CDR-OIDC
    type: openIdConnect
    description: >-
      OpenID Connect identity layer required by the CDR security profile; issuer
      and discovery are published per data holder at the CDR InfoSec baseURI.
    sources: [openapi/regional-australia-bank-cds-banking-products-openapi.yml]

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact 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 security artifact
curl "https://apis.io/api/v1/security/regional-australia-bank-authentication"
All security posture
curl "https://apis.io/api/v1/security?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.