As our platform evolves, we may make changes to our APIs and developer tools. These changes will be released with advance notice and communications will be sent to our developer community via email, blogs, and newsletter, as applicable.
This article details the changes that are scheduled to be launched from November 2025 to January 2026.
What is happening?
We’re introducing the following updates to our Accounting API:
- Webhooks
Our webhooks platform was rebuilt recently and with this update, all app developers on the platform will need to start consuming webhooks notifications in a new CloudEvents format.
You will see a button on the webhooks subscription page that will allow you to switch from the old format to the new format. This switch will allow you to test the new format and do the migration when you’re ready.
More information can be found here.
All developers must complete migration to the new format by May 15, 2026.
- Update to ID field on all entities:
The ID field on all entities will no longer be a sortable field. We recommend you sort results using another field like TxnDate, where available. Taking the Invoice entity as an example, the following query may no longer return results correctly sorted.
- Select * from Invoice ORDERBY Id
These changes will be implemented in Sandbox on December 10, 2025 and in Production on January 27, 2026.
- Employee entity
There is an update to the validation error message being returned on employee address fields, such as PrimaryAddr . Previously, if the API request contained an incorrect address, the error message would specify which address field (city, state, etc) was invalid. This error message is now being updated to “Business Validation Error: INVALID_HOME_ADDRESS”.
The TelephoneNumber field such as PrimaryPhone, Mobile, will be updated to always return formatted phone numbers in the API response. While you will still be able to write any freeform number values to this field, the API response for Update and Read operations will return formatted values only. For example, if you send “1234567890” in the API request, the response will come back as “123-456-7890”.
These changes will be implemented in Sandbox on December 10, 2025 and in Production on January 27, 2026.
- CompanyInfo entity
The CompanyInfo entity includes a list of NameValue objects. The attribute called NeoEnabled will no longer be returned in the response.
These changes will be implemented in Sandbox on December 10, 2025 and in Production on January 27, 2026.
- Update to refresh token expiry
As part of our ongoing effort to enhance security and compliance, we’re introducing significant changes to our refresh token policy. All refresh tokens will now have a maximum validity period of five years. This change ensures that tokens are rotated regularly, reducing the risk associated with long-lived tokens.
Depending on the scopes your app uses, the first set of refresh tokens will start to expire in February 2027 or October 2028.
More information, including detailed timelines and next steps, can be found here.
When will these changes be implemented?
The following changes will be implemented in Sandbox on December 10, 2025:
- The ID field on all entities will no longer be a sortable field.
- Employee entity: address validation error message and phone number format updates.
- CompanyInfo entity: deprecation of NeoEnabled NameValue object
The following changes will be implemented in Production on January 27, 2026:
- The ID field on all entities will no longer be a sortable field.
- Employee entity: address validation error message and phone number format updates.
- CompanyInfo entity: deprecation of NeoEnabled NameValue object
The following change will be available for Sandbox & Production on May 15, 2026:
- Webhooks: Deprecation of old webhooks format
What do I need to do?
Review all the above changes and determine if your app may be impacted or you need to make any code changes.
What if I have additional questions?
If you have additional questions, you can connect with our developer support team by submitting a ticket or asking a question on our forums.
You can also join any of our upcoming office hours to get your questions answered in real time. To sign up for an office hours session, go to the “Webinars and Office Hours” section of the Intuit Developer Support page here.