IMB Bank · Authentication Profile

Imb Bank Authentication

Authentication

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

FinancialBanksOpen BankingCDRConsumer BankingAustraliaMutual BankProduct Reference Data

Methods: none, openIdConnect, oauth2, mutualTLS Schemes: 3 OAuth flows: authorizationCode, clientCredentials, refreshToken API key in:

Security Schemes

PublicProductReferenceData none

CDROpenIDConnect openIdConnect

MutualTLS mutualTLS

Source

Authentication Profile

generated: '2026-07-20'
method: searched
source: https://openbank.openbanking.imb.com.au/.well-known/openid-configuration
docs: https://www.imb.com.au/openbanking
note: IMB's captured OpenAPI (the CDR Banking spec) declares no securitySchemes because
  the public Product Reference Data (PRD) endpoints are unauthenticated. The authenticated
  member-data surface uses the Australian CDR security profile, captured here from
  the live OIDC discovery document.
summary:
  types: [none, openIdConnect, oauth2, mutualTLS]
  public_prd: unauthenticated
  oauth2_flows: [authorizationCode, clientCredentials, refreshToken]
  token_endpoint_auth: private_key_jwt
  profile: FAPI / AU-CDR (acr urn:cds.au:cdr:2)
schemes:
- name: PublicProductReferenceData
  type: none
  description: The GET /banking/products and GET /banking/products/{productId} endpoints
    are public and unauthenticated per the CDR Product Reference Data requirement;
    callers send only x-v (endpoint version) headers.
  applies_to: [listBankingProducts, getBankingProductDetail]
- name: CDROpenIDConnect
  type: openIdConnect
  openIdConnectUrl: https://openbank.openbanking.imb.com.au/.well-known/openid-configuration
  description: Australian Consumer Data Right authorization for member banking data.
    Authorization Code flow with PKCE (S256), Pushed Authorization Requests (RFC 9126,
    required), private_key_jwt client authentication (PS256), and TLS client-certificate-bound
    access tokens (RFC 8705 / FAPI). Response modes fragment and jwt.
  authorization_endpoint: https://auth.openbanking.imb.com.au/oauth2/authorize
  token_endpoint: https://openbank-secure.openbanking.imb.com.au/oauth2/token
  par_endpoint: https://openbank-secure.openbanking.imb.com.au/api/openbanking/push-authorization/par
  jwks_uri: https://openbank.openbanking.imb.com.au/oauth2/jwks
  require_pushed_authorization_requests: true
  tls_client_certificate_bound_access_tokens: true
- name: MutualTLS
  type: mutualTLS
  description: The data-holder resource endpoints are exposed over an mTLS gateway
    (server url pattern https://mtls.dh.example.com/cds-au/v1 in the CDS spec); accredited
    data recipients present a client certificate issued under the CDR trust framework.

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