Up
Up is an Australian digital-only neobank founded in 2018 as a collaboration between Melbourne software company Ferocia and Bendigo and Adelaide Bank. Up is not a mutual and is not separately licensed; it operates as a brand of ASX-listed Bendigo and Adelaide Bank, which holds the Authorised Deposit-taking Institution (ADI) licence, provides the underlying deposit products, and acquired full ownership of Ferocia and Up in 2021. Marketed as Australia's first fully cloud-hosted bank, Up serves more than one million customers through a mobile-first app with no monthly account fees, high-interest savers, and rich transaction categorisation. Up has a strong public API posture for its size - it exposes both a documented personal-banking developer API (accounts, transactions, tags, webhooks) and, as required of every Australian data holder under the Consumer Data Right (CDR / Open Banking), a public, unauthenticated Product Reference Data (PRD) API conforming to the DSB Consumer Data Standards.
Up 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 Banking.
The Up catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Up’s developer surface includes documentation, getting-started guide, engineering blog, pricing, signup flow, support, authentication, and 27 more developer resources.
Kin Score
APIs 14
Individual APIs this provider publishes, each with its own machine-readable definition.
Up 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...
Up Attachments API
Attachments represent uploaded files that are attached to transactions, these are commonly receipts.
Up Banking Account Balances API
Banking Account Balance endpoints
Up Banking Account Direct Debits API
Banking Account Direct Debit endpoints
Up Banking Account Scheduled Payments API
Banking Account Scheduled Payment endpoints
Up Banking Account Transactions API
Banking Account Transaction endpoints
Up Banking Accounts API
Banking Account endpoints
Up Banking Payees API
Banking Payee endpoints
Up Banking Products API
Banking Product endpoints
Up 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...
Up 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...
Up 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...
Up 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!
Up 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.
up-bank-mcp.yml
MCP SERVERRate Limits 1
Documented rate limits and quota policies.
Up Bank Rate Limits
RATE LIMITSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Up Personal Banking Webhooks
Event surface for the Up Personal Banking API. Once a webhook is registered (POST /webhooks), Up delivers JSON-encoded POST callbacks to the configured URL whenever transaction ...
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type