-
Notifications
You must be signed in to change notification settings - Fork 41
blog about Xero pricing changes #1747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pj-simpson
wants to merge
5
commits into
main
Choose a base branch
from
xero-pricing-blog
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b0a3231
blog about Xero pricing changes
28087b3
Fix possessive form in sync frequency note
pj-simpson ccd73ad
Update blog/260116-xero-pricing.md
pj-simpson 2dff1c8
Revise Xero pricing model details and formatting
pj-simpson b0a348b
Set draft status to false for Xero pricing update
pj-simpson File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| --- | ||
| title: "Xero: Updates to developer pricing model" | ||
| date: "2026-01-16" | ||
| tags: ["Xero", "Update"] | ||
| authors: psimpson | ||
| draft: false | ||
| --- | ||
|
|
||
| Xero recently announced an update to its [developer pricing model](https://developer.xero.com/pricing) with plans to introduce a tiered, usage-based pricing structure. This will take effect on 2 March 2026, alongside updates to their Developer Terms and Conditions. | ||
|
|
||
| <!--truncate--> | ||
|
|
||
| ## What’s changing? | ||
|
|
||
| For ecosystem app partners Xero is introducing five pricing tiers based on: | ||
|
|
||
| - Number of customer connections (tenants) linked to your app. | ||
| - API data egress (how much data your app pulls from Xero via the API). | ||
|
|
||
| The tiers each have different connection limits, included API egress usage, and monthly fees. | ||
|
|
||
| ## Why this matters | ||
| Depending on your current connection volumes and API usage, you may need to: | ||
| - Select a tier. | ||
| - Add a payment method in [Xero’s developer portal](http://developer.xero.com/app/manage/) (required once moving beyond Starter). | ||
| - Monitor and optimise API usage to manage costs. | ||
|
|
||
| ## What you should do now | ||
| To avoid disruption and ensure you’re ready ahead of March, we recommend you: | ||
|
|
||
| - Review [Xero’s pricing and tier model](https://developer.xero.com/pricing#tier-fees-connection-limits-and-api-volume-usage). | ||
| - Login to your [Xero developer app](http://developer.xero.com/app/manage/) and check your API usage. | ||
| - Plan for tier selection/billing readiness ahead of March 2026. | ||
| - Please review your datasets' [sync frequency](https://docs.codat.io/using-the-api/queueing-data-syncs#sync-frequency) in the Codat portal. It is always reccomended that you only sync data as often as is essential for your use-case. | ||
pj-simpson marked this conversation as resolved.
Show resolved
Hide resolved
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.