As of March 2, 2026, Xero retired its revenue-share model with developers and moved to tiered, usage-based API pricing. The free access that helped build Xero's ecosystem of 1,000+ apps? Gone. Some developers are now looking at annual bills jumping from near-zero to over $17,000.

And buried in the same update: a blanket prohibition on using any Xero API data to train AI or machine learning models.

If you're building integrations with Xero — or using apps that do — this one matters.

The old model: Developers could access Xero's APIs for free if they billed customers directly outside the Xero App Store. If they sold through the App Store, Xero took 15% of revenue. This encouraged ecosystem growth and made it easy for small developers to build and experiment.

The new model: Five tiers based on two factors — the number of customer connections and data egress (how much data your app pulls from Xero).

The Starter tier keeps things free for early-stage testing, but the cap at 5 connections means you'll hit the paywall fast once you have real users.

The real pain point: if your app needs access to the Journals endpoint or Xero Practice Manager API, you're forced into the Advanced tier at minimum — $10,740/year before any overage charges. One developer told The Register this "would financially eclipse our 2nd highest annual expense by a country mile."

The AI clause: Xero's updated Developer Terms now explicitly prohibit using API data "to train or contribute to the creation of any AI or machine learning model." The stated reason: "to bolster user trust and data security."

This isn't a subtle hint. It's a hard ban. And it applies to all developers as of March 2nd.

Xero isn't a niche player. It has 4.6 million subscribers globally and dominates the SME accounting market in the UK, Australia, and New Zealand. The ecosystem of third-party apps — payroll, payments, expense management, reporting — is a major part of why businesses choose Xero.

That ecosystem was built on free API access. Now, the economics have flipped.

The developers I've seen comment publicly aren't happy. One called it a "rug pull." Another said the new pricing "would have completely killed our ambition to integrate with Xero" if it had existed when they started. RSM Australia's digital advisory director described it as the end of the "all-you-can-eat Xero data buffet."

The downstream effects are already showing up. At least three Xero-connected apps have raised prices since the announcement. Others are evaluating whether to stay in the ecosystem at all.

And the AI ban is significant in its own right. As one developer put it: "They've now created the conditions where AI-native tools are driven to build our own GLs [general ledgers]." If you can't train on Xero data, you might decide to stop depending on Xero entirely.

This isn't just a Xero story. It's part of a broader pattern.

Intuit (QuickBooks) made a similar move in November 2025. Stripe tightened its data policies earlier this year. Amazon banned AI agents from its seller platform. The era of "build whatever you want on our API" is ending. Platforms are locking down, monetizing access, and drawing hard lines around AI training.

For developers and founders, the lesson is uncomfortable: the API you build on today can become expensive — or hostile — tomorrow. The terms can change. The pricing can change. And if you've built your product on someone else's data, you're exposed.

If you're using Xero integrations, expect price increases from your vendors. Some have already happened. More are coming.

If you're building on Xero's API, audit your usage now. Xero's Developer Portal has tools to check your connection count and data egress. Know which tier you'll land in before migration hits your app (mid-March onward, with 30 days notice).

If you're training models on accounting data — or thinking about it — Xero is now off the table. The ban is explicit. Violating it puts your API access at risk.

And if you're evaluating accounting integrations for a new product, consider the full landscape. QuickBooks has its own pricing model. Sage and FreshBooks still offer free API access. A unified API layer (like Apideck or Codat) can hedge against platform-specific pricing changes.

The rules changed. Plan accordingly.

Trish @ StackDrift

This is what StackDrift tracks — vendor policy changes that affect how you build and what you pay. Subscribe to Drift Intel for weekly breakdowns, or check your dashboard to see what's shifted in your stack.

Found this useful? Forward it to a founder who's too busy to read TOS (so... every founder).Got a vendor you want us to track? Reply to this email.

StackDrift · Unsubscribe