Xero API
/practicemanager/3.0/* version retirement
Stops workingSubscribe to Xero APIShare
On May 6, 2027, the Practice Manager API v3.0 will stop working. This change affects all requests made to the /practicemanager/3.0/* endpoints. After this date, these calls will fail as Xero API retires version 3.0 following a twelve-month migration period.
Calls it hits
/practicemanager/3.0/*
What to use instead of these calls
Move calls from /practicemanager/3.0/ to /practicemanager/3.1/, which adds JSON support and field selection.
In Xero API's words
We are deprecating the Xero Practice Manager (XPM) Public API v3.0 and beginning a 12‑month migration period to retire version 3.0.
Facts
- API
- Xero API
api.xero.com - Kind
- Version retirement
- Announced
- April 29, 2026
- Takes effect
- May 6, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Xero API's own pages
Questions
When does this change take effect?
Calls to /practicemanager/3.0/* on Xero API stop working on May 6, 2027.
What happens to calls after May 6, 2027?
They fail from that day.
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.
More from Xero API 8
-
GET /finance.xro/1.0/AccountingActivities/*Removal Stopped working -
/practicemanager/3.1/lead.api/*Removal Stopped working -
/practicemanager/3.0/purchaseorder.api/*Removal Stopped working -
/practicemanager/3.1/supplier.api/*Removal Stopped working -
POST /payroll.xro/1.0/PayItemsBehaviour change Stopped working -
POST /payroll.xro/2.0/employees/{id}/taxBehaviour change Stops workingin 27 days -
/api.xro/2.0/ExpenseClaims*Endpoint removal Stops workingin 87 days -
No date
/api.xro/2.0/Receipts*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before May 6, 2027.