This page documents any currently known issues with the Xero API. If you believe you are encountering a bug with the Xero API, please contact api@xero.com.


General status

Oct 8th, 21:50 (UTC) – Unexpected issues due to recent release

A release at 22:50 UTC on Oct 7th (11:50am Oct 8th NZ local time) caused an unexpected issue on the Xero API whereby requests were inadvertently redirected with a 302 response and an error page to be returned in place of an API response.

This issue was corrected however we are aware of some partners still facing issues with access tokens. We are continuing to investigate the issue and will update this page when we have a resolution. The current work around is for users to reconnect to Xero.

If you have any issues or concerns in relation to this, please email api@xero.com where we will assist.

Update 02:20 Oct 10th (UTC)
We released a fix for access tokens at 01:20 10th Oct (UTC) which has had some positive effects. Some access tokens are still not able to be refreshed after this release. We’re continuing to look into this issue and will update this page when we have more information.

The work around remains for user to reconnect to Xero.

Please contact api@xero.com if you have any questions.

15 Aug 2014 – There are currently two known issues with the Items endpoint:

1. Item descriptions longer than 1000 characters are causing an error on POST.

2. An Item with an AccountCode from an account that has been deleted or archived is throwing an error on POST. The workaround is to make any update to the item via the Xero UI, then future POSTs on that item will be successful.

We are working on a fix to both of these issues and will post to this page when we have a resolution.

Accounting API: Scheduled outages

None planned


Payroll API – Australia: Known issues

There are no current performance/stability issues with the Xero API.

Payroll API – Australia: Scheduled outages

None planned