ANZ Developer API

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

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey3 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the ANZ Developer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ANZ Developer API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ANZ Developer 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

GET STARTED

Start building with ANZ Developer API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ANZ Developer API for, with concrete tasks.

★ 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 Jentic?

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

Credential isolation

Your ANZ partner API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list ANZ accounts' or 'submit a payment', and Jentic returns the matching ANZ operation with its input schema so the agent calls the right endpoint without browsing the developer portal.

Time to first call

FAQs

Specific to using ANZ Developer 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 with Jentic One, the self-hosted execution layer.

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 Jentic One instance 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.

Can I limit what my agent is allowed to do with the ANZ Developer API?

Yes. Jentic One is self-hosted, so you run your own instance and your own rules decide which ANZ operations the agent may call and which credentials it may use. You can allow only read operations, such as listing accounts with GET /accounts and fetching transaction history with GET /transactions, and leave submitting a domestic payment out of the allowed set. POST /payments is a separate operation that the agent can reach only if you explicitly include it, so an agent scoped to reads cannot move money.