From b0a323148f516900ed009ab17ac998cbbdba5231 Mon Sep 17 00:00:00 2001 From: Peter Simpson Date: Fri, 16 Jan 2026 15:31:21 +0000 Subject: [PATCH 1/5] blog about Xero pricing changes --- blog/260116-xero-pricing.md | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 blog/260116-xero-pricing.md diff --git a/blog/260116-xero-pricing.md b/blog/260116-xero-pricing.md new file mode 100644 index 000000000..9e9499957 --- /dev/null +++ b/blog/260116-xero-pricing.md @@ -0,0 +1,33 @@ +--- +title: "Xero: Updates to developer pricing model" +date: "2026-01-16" +tags: ["Xero", "Update"] +authors: psimpson +--- + +Xero recently announced an update to its [developer pricing model](https://developer.xero.com/pricing?utm_source=sfmc&utm_medium=email&utm_campaign=&utm_content=&sfmc_key=c8b1eeda830671f40b83388d8b0e1207051d1b09-R0wgNDg0NSBPIE9USCBPVEggLSBQcm9qZWN0IFNlbnRpbmVsIC0gRW1haWwgIzEgLSBNYWluIEVtYWls) 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. + + + +## 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?utm_source=sfmc&utm_medium=email&utm_campaign=&utm_content=&sfmc_key=c8b1eeda830671f40b83388d8b0e1207051d1b09-R0wgNDg0NSBPIE9USCBPVEggLSBQcm9qZWN0IFNlbnRpbmVsIC0gRW1haWwgIzEgLSBNYWluIEVtYWls#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 dataset's [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. \ No newline at end of file From 28087b3e13f4a55391d2a02123ca35a50250015f Mon Sep 17 00:00:00 2001 From: Peter Simpson <40800258+pj-simpson@users.noreply.github.com> Date: Fri, 16 Jan 2026 15:33:17 +0000 Subject: [PATCH 2/5] Fix possessive form in sync frequency note Corrected the possessive form of 'dataset' to 'datasets' in the sync frequency recommendation. --- blog/260116-xero-pricing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/260116-xero-pricing.md b/blog/260116-xero-pricing.md index 9e9499957..3ad5d5494 100644 --- a/blog/260116-xero-pricing.md +++ b/blog/260116-xero-pricing.md @@ -30,4 +30,4 @@ 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?utm_source=sfmc&utm_medium=email&utm_campaign=&utm_content=&sfmc_key=c8b1eeda830671f40b83388d8b0e1207051d1b09-R0wgNDg0NSBPIE9USCBPVEggLSBQcm9qZWN0IFNlbnRpbmVsIC0gRW1haWwgIzEgLSBNYWluIEVtYWls#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 dataset's [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. \ No newline at end of file +- 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. From ccd73ada533584c6424e480b285660722f1a4036 Mon Sep 17 00:00:00 2001 From: Peter Simpson <40800258+pj-simpson@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:02:02 +0000 Subject: [PATCH 3/5] Update blog/260116-xero-pricing.md Co-authored-by: Mattt --- blog/260116-xero-pricing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/260116-xero-pricing.md b/blog/260116-xero-pricing.md index 3ad5d5494..e956d94a0 100644 --- a/blog/260116-xero-pricing.md +++ b/blog/260116-xero-pricing.md @@ -27,7 +27,7 @@ Depending on your current connection volumes and API usage, you may need to: ## 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?utm_source=sfmc&utm_medium=email&utm_campaign=&utm_content=&sfmc_key=c8b1eeda830671f40b83388d8b0e1207051d1b09-R0wgNDg0NSBPIE9USCBPVEggLSBQcm9qZWN0IFNlbnRpbmVsIC0gRW1haWwgIzEgLSBNYWluIEVtYWls#tier-fees-connection-limits-and-api-volume-usage) +- 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. From 2dff1c89be232ad174b3344969df57184d35a1a5 Mon Sep 17 00:00:00 2001 From: Peter Simpson <40800258+pj-simpson@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:04:04 +0000 Subject: [PATCH 4/5] Revise Xero pricing model details and formatting Updated the Xero pricing model article to improve clarity and fix formatting issues. --- blog/260116-xero-pricing.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/blog/260116-xero-pricing.md b/blog/260116-xero-pricing.md index e956d94a0..a2600e68a 100644 --- a/blog/260116-xero-pricing.md +++ b/blog/260116-xero-pricing.md @@ -5,7 +5,7 @@ tags: ["Xero", "Update"] authors: psimpson --- -Xero recently announced an update to its [developer pricing model](https://developer.xero.com/pricing?utm_source=sfmc&utm_medium=email&utm_campaign=&utm_content=&sfmc_key=c8b1eeda830671f40b83388d8b0e1207051d1b09-R0wgNDg0NSBPIE9USCBPVEggLSBQcm9qZWN0IFNlbnRpbmVsIC0gRW1haWwgIzEgLSBNYWluIEVtYWls) 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. +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. @@ -13,21 +13,21 @@ Xero recently announced an update to its [developer pricing model](https://devel 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) +- 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) +- 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 +- 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. From b0a348bbde7c8f3780d1f365dc2c696d6fea6d57 Mon Sep 17 00:00:00 2001 From: Peter Simpson <40800258+pj-simpson@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:09:03 +0000 Subject: [PATCH 5/5] Set draft status to false for Xero pricing update --- blog/260116-xero-pricing.md | 1 + 1 file changed, 1 insertion(+) diff --git a/blog/260116-xero-pricing.md b/blog/260116-xero-pricing.md index a2600e68a..63caa6ff1 100644 --- a/blog/260116-xero-pricing.md +++ b/blog/260116-xero-pricing.md @@ -3,6 +3,7 @@ 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.