Xero API pricing changes in 2026: what they mean for your custom integrations

If your firm uses Xero, you have probably heard that Xero started charging for API access in 2026, and perhaps an app vendor has already written to say its prices are going up. The natural worry is whether the integrations you rely on, or the custom one a developer built for you, are about to cost more or stop working.

The direct answer: since March 2, 2026, Xero charges app developers through five tiers based on how many Xero organizations an app connects to and how much data it pulls out. For most small firms the bill lands on the app vendors, not on you, and Xero says bespoke integrations built for your own practice or a single client are exempt. What does affect firms directly is a short list: the Journals endpoint now sits behind the top paid tier, data use for AI training is prohibited, and some app vendors are passing costs on. Here is what changed and what to check.

What Xero changed

Xero's pricing and policy updates FAQ sets out the new model. Apps registered from December 4, 2025 were on the new developer terms straight away; earlier apps moved onto them from March 2, 2026, with existing apps migrated from mid-March after at least 30 days' notice.

The tiers, as listed on Xero's developer pricing page in October 2026, in Australian dollars and excluding tax:

A few rules sit underneath the table, all from the same two Xero pages:

• Only data going out is metered. Xero calls it egress. Sending data into Xero (creating invoices, contacts, payments) is unlimited on every tier. Above the included allowance, Core, Plus and Advanced pay AUD 2.40 per GB.
• Limits are per app. Two apps from the same developer cannot share connections or data allowances.
• Allowances reset monthly on the first of the calendar month (UTC), which is also the billing cycle. Payment is by credit card.
• Starter and Core apps cannot be listed on the Xero App Store. Enterprise requires a listing.

Who is exempt

This is the part most owners need. Xero's FAQ says:

• Bespoke integrations built for your own accounting practice or for a single client are exempt from the new pricing model.
• Custom Connections keep their existing commercial terms. Custom Connections are Xero's product for a private, single-organization integration, sold separately.
• Financial services apps (banking, credit, payments), conversion-only partners and franchise-network apps are also excluded.

So if a developer built one integration that connects your firm's Xero to your CRM or practice management system, and it is used only by your firm, it should not suddenly carry a tier fee. Confirm with whoever built it how the app is registered, because the exemption depends on that, not on how small you are.

Where firms do feel it

The apps you pay for may cost more

Your CRM, practice management, payroll or reporting tool connects to thousands of Xero organizations, so its vendor now pays Xero for the Plus, Advanced or Enterprise tier, plus data volume. Some will absorb it; some will pass it on through price rises, new "Xero connector" add-ons or reduced sync frequency. If a vendor's renewal arrives with a new line item, this is usually why.

Zapier and Make connect to Xero through their own registered apps, so the tier fee is theirs. Your cost there is still the automation platform's own plan, priced in tasks or credits as before.

The Journals endpoint moved behind the Advanced tier

Xero's FAQ says the Journals endpoint, the Xero Practice Manager API and Bulk Connections are available only from the Advanced tier, and require an initial and annual security assessment plus approval of the use case. Manual Journals are a separate endpoint and remain available on all tiers.

This matters for reporting. Many dashboards, consolidation tools and custom reports read the full general ledger through the Journals endpoint. A small reporting app on a lower tier, or a custom report a freelancer built for several clients, may lose that access. If your management reporting depends on a Xero data feed, ask the provider which endpoint it uses and which tier it is on.

Accounting practices that built their own tools

An accounting or bookkeeping firm that built a tool for its own use is covered by the "own practice" exemption. A firm that built one tool and connects it to many clients' Xero organizations should read the FAQ closely and check with Xero how that app is classed, because the exemption wording covers your own practice or a single client. Our article on integrations for accounting firms covers the wider stack.

AI use of Xero data

Xero's updated developer terms, as summarized in the FAQ, prohibit using data obtained through the Xero APIs to train or help create any AI or machine learning model, and prohibit bots or browser extensions that simulate user actions to get around Xero's security controls. If you are planning an AI assistant that reads your Xero data, check how the tool uses that data and read the terms with whoever is building it.

What to check this month

1. List what is connected. Xero shows the apps connected to your organization in its settings. Note each app, what it does and who in the firm owns it. Disconnect anything nobody uses; a forgotten connection is also an unnecessary route into your financial data.
2. Ask your key vendors two questions. Has the Xero pricing change affected your price or features for us? Do you use the Journals endpoint, and if so, will access continue?
3. Check any custom integration. Ask whoever built it how the app is registered (a Custom Connection, a private app for your firm, or an app shared with other clients) and whether it reads journals.
4. Look at how much data it pulls. A custom sync that downloads every invoice and contact on every run uses far more data than one that fetches only records changed since the last run, or that reacts to Xero's webhooks. Even when you are exempt, a leaner sync is faster and less likely to hit the daily call limit.
5. Watch renewals. Note which Xero-connected subscriptions renew in the next six months and diary a check a month before each.

Check with your accountant before swapping a reporting or payroll tool because of a price change; the cheapest replacement can cost more in reconciliation time.

Should you rebuild anything?

Usually not straight away. The integrations most worth reviewing are the ones that read large amounts of data out of Xero on a schedule, depend on the Journals endpoint, or were built once and quietly reused for several organizations. If one of those breaks or becomes expensive, it is a good moment to ask whether the job still needs doing in that way, for example whether a won deal in HubSpot creating a Xero invoice needs a custom app at all, or whether the native connector or an automation platform now covers it.

How Flow Mesh helps

Every engagement starts with a first call, then a stack audit scoped in writing before it starts. It gives a verdict on every tool connected to your Xero (keep, configure, consolidate or replace) and a written scope for any integration worth rebuilding. Builds are quoted in writing after the audit and run inside your own accounts.

Key takeaways

• Since March 2, 2026, Xero charges app developers by tier, connected organizations and data pulled out; sending data into Xero is unlimited.
• Bespoke integrations for your own practice or a single client are exempt, and Custom Connections keep their existing terms.
• The Journals endpoint now needs the Advanced tier and a security assessment; Manual Journals stay available on all tiers.
• Xero's terms prohibit using API data to train AI models; check any AI tool you connect.
• List your connected apps, ask key vendors about price and Journals access, and make custom syncs fetch only what changed.