How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Bendigo and Adelaide Bank website screenshot

Bendigo and Adelaide Bank

Bendigo and Adelaide Bank Limited (ASX:BEN) is one of Australia's largest retail banks, formed by the 2007 merger of the community-focused Bendigo Bank and the wholesale-strong Adelaide Bank, and headquartered in Bendigo, Victoria. The group serves millions of customers through the Bendigo Bank, Adelaide Bank, Rural Bank, and Up (neobank) brands, with a distinctive Community Bank branch-franchise model. As an authorised deposit-taking institution and accredited Consumer Data Right (CDR) data holder, the bank exposes public, unauthenticated Product Reference Data (PRD) APIs conforming to the Australian Consumer Data Standards, alongside the authenticated CDR consumer data-sharing surface governed by the ACCC/DSB rules.

agent ready

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Bendigo and Adelaide Bank the way a machine reads it — 34 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Bendigo and Adelaide Bank scores 40.8/100 (developing), with a separate agent-readiness read of 44/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-10 · rubric v0.20.0
Bendigo and Adelaide Bank Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Bendigo and Adelaide Bank's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bendigo-and-adelaide-bank/"
   title="Bendigo and Adelaide Bank on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/bendigo-and-adelaide-bank.svg"
       alt="Bendigo and Adelaide Bank Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Bendigo and Adelaide Bank

Each block below is one kind of artifact we hold for Bendigo and Adelaide Bank. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 14

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Bendigo and Adelaide Bank Accounts API

Accounts represent the underlying store used to track balances and the transactions that have occurred to modify those balances over time. Up currently has three types of accoun...

Bendigo and Adelaide Bank Attachments API

Attachments represent uploaded files that are attached to transactions, these are commonly receipts.

Bendigo and Adelaide Bank Banking Account Direct Debits API

Banking Account Direct Debit endpoints

Bendigo and Adelaide Bank Banking Account Scheduled Payments API

Banking Account Scheduled Payment endpoints

Bendigo and Adelaide Bank Banking Account Transactions API

Banking Account Transaction endpoints

Bendigo and Adelaide Bank Categories API

Categories enable understanding where your money goes by driving powerful insights in Up. All categories in Up are pre-defined and are automatically assigned to new purchases in...

Bendigo and Adelaide Bank Tags API

Tags are custom labels that can be associated with transactions on Up. Within the Up application, tags provide additional insight into spending. For example, you could have a "T...

Bendigo and Adelaide Bank Transactions API

Transactions represent the movement of money into and out of an account. They have many characteristics that vary depending on the kind of transaction. Transactions may be tempo...

Bendigo and Adelaide Bank Utility endpoints API

Some endpoints exist not to expose data, but to test the API itself. Currently there is only one endpoint in this group: ping!

Bendigo and Adelaide Bank Webhooks API

Webhooks provide a mechanism for a configured URL to receive events when transaction activity occurs on Up. You can think of webhooks as being like push notifications for your s...

Scroll within the panel for all 14 ·

Open Collections 15

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 15 ·

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Up Developer API Webhooks

Real-time webhook event callbacks delivered by Up to a subscriber-configured HTTPS URL when transaction activity occurs on an Up account. Each delivery carries an X-Up-Authentic...

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Bendigo And Adelaide Bank Authentication

none/openIdConnect/oauth2/mutualTLS · 3 schemes

SECURITY

Bendigo And Adelaide Bank Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Bendigo And Adelaide Bank Vulnerability Disclosure

disclosure policy published

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Bendigo And Adelaide Bank Scopes

10 scopes · authorizationCode/clientCredentials

10 scopes

SCOPES

Resources

Every other property we hold for Bendigo and Adelaide Bank — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Build 2

SDKs, sample code, and the tooling you integrate with

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/bendigo-and-adelaide-bank · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Bendigo and Adelaide Bank, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.