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.
Bendigo and Adelaide Bank publishes 14 APIs on the APIs.io network, including Accounts API, Attachments API, Banking Account Balances API, and 11 more. Tagged areas include Financial, Banks, Open Banking, CDR, and Consumer Data Right.
The Bendigo and Adelaide Bank catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Bendigo and Adelaide Bank’s developer surface includes developer portal, documentation, support, engineering blog, authentication, and 26 more developer resources.
Kin Score
APIs 14
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 Balances API
Banking Account Balance endpoints
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 Banking Accounts API
Banking Account endpoints
Bendigo and Adelaide Bank Banking Payees API
Banking Payee endpoints
Bendigo and Adelaide Bank Banking Products API
Banking Product 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 for all 14
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
bendigo-and-adelaide-bank-mcp.yml
MCP SERVEREvent Specifications 1
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...
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
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
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 4
Properties that don't map to a standard resource type