An ANZ API for your own accounts.

Connect ANZ once through the Consumer Data Right. Read your transactions and balances as JSON with a scoped key, or ask an AI agent over MCP. No accreditation, no ABN, no sales call.

  • read-only · CDR regulated
  • 7 years of history
  • from US$7/mo
ANZapi.banksync.ioAU · CDR
$curl https://api.banksync.io/v1/banks/bnk_anz/accounts/acc_6604/transactions?from=2026-09-01 \     -H "X-API-Key: bsk_live_…" {  "success": true,  "data": [    { "date": "2026-10-08", "description": "Woolworths Surry Hills", "amount": -84.20, "category": "Groceries" },    { "date": "2026-10-07", "description": "Opal Card Top Up", "amount": -40.00, "category": "Transport" },    …41 more  ],  "meta": { "count": 43, "hasMore": false }}200 OK · 43 rows · 118 ms
Example GET request to the BankSync API and its JSON response.

ANZ and personal API access

ANZ does not hand customers an API key for their own accounts; the regulated route is a Consumer Data Right (CDR) consent, which is what BankSync uses.

You approve sharing on ANZ’s own CDR consent screen, pick the accounts and how long the consent lasts (up to 12 months), and BankSync receives the data as a CDR Representative of Fiskil Pty Ltd (ADRBNK000246). Your key reads it back as JSON.

What you get in Australia

Data
Transactions and balances. Read-only.
History
Up to 7 years on the first sync.
Consent
Up to 12 months, then you approve again at your bank.
Framework
Consumer Data Right · ACCC & Treasury
Provider
BankSync is a CDR Representative of Fiskil Pty Ltd, an Accredited Data Recipient (ADRBNK000246).

How it works

  1. 1

    Connect your own bank

    Sign up, then connect ANZ through your bank's own consent screen.

  2. 2

    Create an API key

    Workspace › Developers. Give it only the scopes it needs; revoke it any time.

    banks:read
  3. 3

    Make your first call

    Read transactions and balances as JSON with one GET request and your key in the X-API-Key header.

  4. 4

    Or ask an AI agent

    Point Claude, ChatGPT or Cursor at the MCP server and ask questions about the same data.

    MCP

Call it your way

$curl -s "https://api.banksync.io/v1/banks/bnk_anz/accounts/acc_6604/transactions?from=2026-09-01" \     -H "X-API-Key: bsk_live_…" \     | jq '.data[] | {date, description, amount}'

API access from $7/mo

Standard includes 5 bank connections, 10 API requests a minute and the MCP server. Every plan starts with a 14-day free trial. Prices shown in USD.

Frequently asked questions

Does ANZ offer a personal API?

ANZ does not hand customers an API key for their own accounts; the regulated route is a Consumer Data Right (CDR) consent, which is what BankSync uses.

What data can I read from my ANZ accounts?

Transactions and balances, read-only, as JSON. The first sync reaches back up to 7 years; how far back ANZ actually returns can vary by account.

How long does consent last?

A CDR consent lasts up to 12 months; you choose the duration on ANZ’s consent screen. When it ends, reconnect from the app and approve again. You can withdraw consent at any time from ANZ or from BankSync.

Is the API read-only?

Yes. The connection your bank grants is read-only: BankSync can read account data, and it cannot move money, make payments or change anything at your bank. Your API key reads the same data, scoped to the permissions you give it.

Can I use my ANZ data with Claude or ChatGPT?

Yes. The same read-only data is available over BankSync’s MCP server: point Claude, ChatGPT or Cursor at it and ask about your ANZ transactions in plain English. It is included from the Standard plan.

What about ANZ business accounts?

Which business and commercial accounts ANZ shares varies, so we do not promise them here. Contact support with your account type before you rely on it, and we will tell you what connects.

Other Australian banks

The same key reads every bank you connect.

Read your ANZ data tonight

Connect ANZ, create a scoped key, and read your own data as JSON.