The QuickBooks Online Accounting API uses minor versions to introduce incremental changes while maintaining backward compatibility for existing clients. Developers using the API can specify a minor version to access a particular version of the API. For example, if a developer is using minor version 44 and a new schema change is introduced, the new schema change will be available in minor versions equal to or greater than 45.
Beginning August 1, 2025, we will be deprecating support for minor versions 1–74. All API requests to the Accounting API will use the minor version 75 by default and previous minor versions will be ignored.
This update doesn’t apply to users of our Desktop, Payments or Payroll APIs, as these APIs don’t use minor versions.
How does this impact me?
In your API request, if you specify a value for the minorversion parameter that is less than 75, it will be ignored and the system will respond with data corresponding to minor version 75.
If you don’t specify a minor version in your request, the response will default to minor version 75 rather than the base version.
Any future updates to the Accounting API that aren’t backward compatible will be released under new minor versions (for example, field or feature removals, and updates to enum fields). However, changes such as the addition of new fields to the schema won’t trigger a minor version update. This will ensure that all apps benefit from any bug fixes or new features without having to maintain minor versions. Details of new features will be included in future release notes and newsletters.
How do I know which minor version I’m using?
In your app’s code, you may be passing a parameter called minorversion in your API request. Your API request may look like this:
https://quickbooks.api.intuit.com/v3/company/<realmId>/<apiEntity>/entityId?minorversion=<minorVersionValue>Here are some examples –
POST https://quickbooks.api.intuit.com/v3/company/1234/item?minorversion=65GET https://quickbooks.api.intuit.com/v3/company/1234/invoice/101?minorversion=65In the above requests, the minor version is 65.
How do I know what changes were made after the minor version I’m currently using?
Our minor version document lists the features included in each minor version.
For example, if your app currently uses minor version 62, you should review the features added in minor versions 63 and later. Once minor version 62 is deprecated and your app is upgraded to minor version 75, all these new features will be available to you.
What do I need to do?
- If you aren’t using minor versions in your API requests, ensure your code is compatible with minor version 75 and the corresponding schema.
- If you are using minor versions in your API requests, update your requests to use minor version 75. For example, your requests may look like this:
https://quickbooks.api.intuit.com/v3/company/<realmId>/<apiEntity>/entityId?minorversion=75- If you are using our Java SDK, then update it to the latest version 6.5.0
- If you are using our PHP SDK, then update it to the latest version 6.2.0
- If you are using our .Net SDK, then update it to the latest version 14.7.0
- If you aren’t using any of our SDKs, ensure your code is compatible with minor version 75 and the corresponding schema.
- Ensure your code can handle future additions to the schema. You can do this by ignoring unknown fields so your app isn’t impacted when we release new fields in the future.
When do I need to take action?
Be sure you take action by July 31, 2025. Although we will implement this change in a phased manner, the API will start returning responses for minor version 75 beginning August 1, 2025.
How do I test my changes?
Starting February 10, 2025, you can use our sandbox environment to thoroughly test your application for compatibility with minor version 75 or later. Support for minor versions 1–74 in this environment will end on February 10, 2025.
I don’t use minor versions. Will my app be impacted by this change?
Yes. If you don’t use a minor version, our platform treats your API requests as though they were using the base version, minor version 1, by default. With this change, the base version will be minor version 75, instead of minor version 1. All the changes from minor version 1–75 will be applicable to your app. Ensure your code is compatible with minor version 75 and the corresponding schema. We recommend that you test your integration in the sandbox before July 31, 2025.
What happens if I don’t take any action?
Depending on how you are processing our Accounting API response, your app may be negatively affected if it doesn’t handle new API fields introduced in the latest minor versions.
What if I have additional questions?
Connect with our developer support team by submitting a ticket or asking a question on our forums.