Avenue Bank · Authentication Profile

Avenue Bank Authentication

Authentication

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

FinancialBanksOpen BankingCDRConsumer Data RightConsumer BankingBusiness BankingBank GuaranteesAustraliaADI
Methods: none, oauth2, openIdConnect, mutualTLS Schemes: 2 OAuth flows: authorizationCode API key in:

Security Schemes

public none
cdr-oauth2 oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://consumerdatastandardsaustralia.github.io/standards/#security-profile
docs: https://consumerdatastandardsaustralia.github.io/standards/#security-profile
note: The harvested OpenAPI declares no securitySchemes (it is the bare shared DSB Consumer Data Standards
  Banking API contract). Authentication is defined by the CDR (Consumer Data Right) security profile every
  Australian ADI data holder implements, documented here against the standard. Avenue's live registered
  data-holder status is unverified (API host returned HTTP 403 WAF on 2026-07-21).
summary:
  types:
  - none
  - oauth2
  - openIdConnect
  - mutualTLS
  public_surface: Product Reference Data (Get Products, Get Product Detail) is public and unauthenticated.
  protected_surface: All account/balance/transaction/payee/direct-debit/scheduled-payment/instalment families
    require CDR consumer authorisation.
  oauth2_flows:
  - authorizationCode
profile:
  standard: CDR Security Profile (FAPI 1.0 Advanced profile, AU adaptation)
  oidc: OpenID Connect with the Hybrid/Authorization Code flow; consumer authorises data sharing.
  par: Pushed Authorization Requests (PAR) required.
  client_auth: private_key_jwt (asymmetric).
  token_binding: MTLS-bound (certificate-bound) access tokens; holder-of-key.
  consent_model: Accredited Data Recipient (ADR) requests consumer consent; sharing arrangement with lifetime
    and scopes.
  request_headers:
  - x-v
  - x-min-v
  - x-fapi-interaction-id
  - x-fapi-auth-date
  - x-fapi-customer-ip-address
  - x-cds-client-headers
schemes:
- name: public
  type: none
  applies_to:
  - listBankingProducts
  - getBankingProductDetail
  note: PRD endpoints require no authentication per the standard.
- name: cdr-oauth2
  type: oauth2
  flow: authorizationCode
  note: CDR ADR consumer-authorised access for all non-PRD families; scopes in scopes/avenue-bank-scopes.yml.
  sources:
  - openapi/avenue-bank-cds-banking-openapi.json

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

GitHub Google LinkedIn

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