ANZ Developer API

Name: ANZ Developer API API
Brand: ANZ Developer API
Availability: InStock

★ Only Publicly Available SpecFinanceBankingapiKey3 EndpointsREST

For Agents

List ANZ Bank accounts, fetch transaction history, and submit payments via an API-key-protected partner endpoint.

Quickstart

Get started with ANZ Developer API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list ANZ accounts"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ANZ Developer API API.

List ANZ customer accounts that the calling partner is authorised to read

Retrieve transaction history for an authorised account, including amount, date, and counterparty

Submit a domestic payment instruction from an authorised ANZ account

Authenticate as an accredited partner using an API key in the Authorization header

Use Cases

GET STARTED

Start building with ANZ Developer API API

Explore with Jentic

View OpenAPI Spec

Use for: I need to list a customer's ANZ accounts, Retrieve recent transactions on an ANZ account, Submit a payment from an ANZ account, Check the balance of an ANZ account

Not supported: Does not handle card acceptance, foreign exchange, or international wires - use for listing ANZ accounts, fetching transactions, and submitting domestic payments only.

Jentic publishes the only available OpenAPI specification for ANZ Developer API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ANZ Developer API, keeping it validated and agent-ready. ANZ is one of Australia's four major banks and exposes a developer API for accessing customer accounts, listing transactions, and submitting payments. The current surface area is intentionally small (three endpoints) and is intended for accredited partner integrations under Australia's Consumer Data Right and similar partner programs. Authentication is an API key in the Authorization header.

★ Account aggregation for a partner finance app

Pull a customer's ANZ account list and recent transactions into a partner finance application for budgeting, reconciliation, or expense categorisation. The agent calls /accounts to enumerate accounts and /transactions for the chosen account, then maps the data into the host app's schema. This avoids screen-scraping the consumer banking site and works under accredited partner agreements.

GET /accounts to list authorised accounts, then GET /transactions filtered to the last 30 days for each account and map them into the host app's ledger

Initiate a partner payment

Submit a domestic payment from an authorised ANZ account on behalf of a customer who has consented through the partner program. The agent posts payee details, amount, and reference to /payments and stores the resulting payment id for reconciliation against the next /transactions pull.

POST to /payments with {fromAccount, toAccount, amount, reference} and store the returned payment id for reconciliation

Reconciliation against accounting software

Pull ANZ transactions on a schedule and reconcile them against entries in an accounting tool such as Xero. The agent calls /transactions for each account, matches each line against an open invoice or expense, and flags anything unmatched for human review. This shortens month-end close for partner-onboarded business accounts.

GET /transactions for each account in the last full month, fuzzy-match each line to an open Xero invoice, and tag unmatched lines for human review

AI agent integration via Jentic

An agent supporting a partner-onboarded ANZ customer can search Jentic for 'list ANZ accounts' or 'submit a payment from an ANZ account' and call the right endpoint without handling the partner API key. The key is held server-side by Jentic and injected per call.

Search Jentic for 'list ANZ accounts', load the /accounts schema, and call it for the consented partner customer

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for anz developer api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/accounts

List ANZ accounts authorised to the partner

GET

/transactions

List transactions for an authorised account

POST

/payments

Submit a domestic payment from an ANZ account

GET

/accounts

List ANZ accounts authorised to the partner

GET

/transactions

List transactions for an authorised account

POST

/payments

Submit a domestic payment from an ANZ account

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ANZ partner API keys are stored in the Jentic vault (MAXsystem) and never enter the agent context. Jentic attaches the Authorization header server-side and isolates customer-consent context per call.

Intent-based discovery

Agents search Jentic by intent ('list ANZ accounts', 'submit a payment') and Jentic returns the matching ANZ endpoint and its schema, so the agent does not need to read the partner developer portal.

Time to first call

Direct integration: weeks to months due to ANZ's partner accreditation process. Through Jentic: the API call itself is under an hour once accreditation is in place - search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Plaid API

Multi-bank account aggregation across thousands of institutions in the US, EU, and UK.

Pick Plaid when the agent needs to cover many banks at once, including non-Australian institutions; pick ANZ when the integration is direct partner-to-bank for a single Australian institution.

Alternative

TrueLayer API

Open banking for the UK and EU with payment initiation and account info.

Pick TrueLayer when the agent needs UK or EU open banking; pick ANZ when working directly with an Australian customer's ANZ accounts.

Complementary

Stripe API

Card and wallet payment acceptance, distinct from bank-to-bank transfers.

Use Stripe to accept card payments from customers, and ANZ /payments to move money between ANZ accounts after settlement.

FAQs

Specific to using ANZ Developer API API through Jentic.

Why is there no official OpenAPI spec for ANZ Developer API?

ANZ does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ANZ Developer API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ANZ Developer API use?

An API key passed in the Authorization header (apiKey scheme), issued to accredited partners through ANZ's developer portal. Through Jentic the key is held in the encrypted MAXsystem vault and attached server-side per request, so the secret never enters the agent context.

Can I list a customer's ANZ accounts and transactions with this API?

Yes. GET /accounts returns the accounts the partner is authorised to see and GET /transactions returns transaction history for an authorised account. Both require an accredited partner key and a customer consent established through ANZ's partner onboarding.

How do I submit a payment from an ANZ account through Jentic?

Search Jentic for 'submit a payment from an ANZ account', load the /payments schema, and POST the from account, to account, amount, and reference. Jentic injects the partner API key and returns the payment id for reconciliation.

Is the ANZ Developer API free to use?

Access is restricted to accredited partner agreements rather than self-serve sign-up. Pricing is negotiated per partner and is not publicly listed; check ANZ's developer portal at developer.online.anz.com for current programs.

What are the rate limits for the ANZ Developer API?

Limits depend on the partner tier and are not declared in the OpenAPI spec. Sandbox keys have lower per-minute caps than production partner keys; the partner agreement specifies the production quota.