Xero API
- Accounting API
- Assets API
- Bank Feeds API
- Files API
- Finance API
- Identity API
- Projects API
- Payroll AU API v2
- Payroll NZ API
- Payroll UK API
Vendor coverage
Xero API changes & breaking changes
Accounting integrations fail quietly: a changed field in an invoice response doesn't crash anything, it just mis-books. Detektu diffs Xero's published OpenAPI contracts so ledger-relevant changes surface as findings, not month-end discrepancies.
Last checked Oct 20, 2026, 4:06 PMLast change detected Sep 4, 2026, 3:53 AM
Detected changes
Latest Xero API changes
Every entry is a change Detektu detected in Xero's published contracts, with exact before/after evidence on its page.
No breaking changes on record yet.
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How Xero ships changes
The release patterns that shape your integration risk.
Xero publishes per-domain OpenAPI contracts. Accounting is the flagship, alongside Assets, Bank Feeds, Files, Finance, Identity, Projects, and region-specific Payroll (AU, NZ, UK). Payroll in particular changes on regulatory schedules that have nothing to do with your release calendar.
Detektu diffs each contract independently and reports the exact operation and field, so a schema change in AU payroll stays quiet for a UK-only integration while a changed invoice field escalates for everyone booking revenue through it.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Field type changed on invoice line items
openapi:GET /Invoices/{InvoiceID} ::response.200.LineItems.TaxAmountNew endpoint in UK payroll
openapi:GET /StatutoryLeaveBalance/{EmployeeId}Monitored for you
Do Xero's changes affect your integration?
Choose the operations and fields your services use. Detektu matches Xero findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.