/api.xro/2.0/Receipts* → endpoint removal

Deprecated, no date

The Receipts endpoint has been deprecated without a shutdown date. This deprecation affects all calls matching /api.xro/2.0/Receipts*, which will ultimately fail. The provider announced on July 31, 2025, that it is deprecating the endpoint.

Calls it hits

/api.xro/2.0/Receipts*

What to use instead of these calls

Stop creating draft expense claim receipts and instead record spend using PUT /api.xro/2.0/BankTransactions or bills via PUT /api.xro/2.0/Invoices with Type ACCPAY. This move requires more than changing an identifier, as receipts belong to the retiring Classic Expenses product and switching alters how expenses are recorded.

Receipts belong to the retiring Classic Expenses product; moving to bills or bank transactions changes how expenses are recorded.

In Xero API's words

We will also be deprecating the Receipts endpoint.

Xero API, Announcement

Facts

API: Xero API api.xero.com
Kind: Endpoint removal
Announced: July 31, 2025
Takes effect: No date given yet
Calls after that day: Fail
Source: Announcement
Last updated: October 26, 2026
Verified: October 27, 2026, against Xero API's own pages

Questions

When does this change take effect?

Xero API deprecated /api.xro/2.0/Receipts* without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Xero API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub