Upcoming changes to the Accounting API

As our platform evolves, we may make changes to our APIs. 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 August to October 2025. If you don’t use our Accounting API, the changes below won’t impact you. 

What is happening?

We’re making a few additions to our throttling limits. These new limits are in addition to the throttling limits already in place for our platform.  

1. In Sandbox, API calls will be throttled at 10 requests per second, per realm ID and app. This puts it on par with our Production limits. This limit will be implemented on September 15, 2025. 

2. In Sandbox and Production, we’re introducing a new limit on the Batch endpoint. API calls to our Batch endpoint will be throttled at 120 requests per minute per realm ID. This limit will be implemented on August 15, 2025 in the Sandbox environment and on October 31, 2025 in the Production environment. 

We’re introducing the following updates to our Accounting API:

Note: Changes to address fields may apply to other entities in the future. If this happens, we will implement the changes in a phased approach, after sufficient advance notification. 

2. Class and Department entities:

The QuickBooks Online product has usage limits that vary by subscription tier. These limits define how many classes and locations you can add to QuickBooks. Get more info here. We will now apply the same limits to data created via the Class and Department APIs. Starting September 15, 2025, the API will be subjected to the same usage limits as the product allows. The QuickBooks Online Plus SKU allows a user to create up to 40 combined classes and locations (i.e. departments). If you try to create more classes or departments, you will start to receive this error:

   

{
  "Message": "Usage Limit Exceeded",
  "Detail": "Usage Limit Exceeded: To add a new class, upgrade or learn how to manage your usage limits. <br/> <a href='https://quickbooks.intuit.com/community/Help-Articles/What-are-usage-limits-in-QuickBooks-Online/m-p/228520' target=\"_blank\"><b>Learn more</b></a>",
  "code": "6570",
  "element": ""
}

This change will be implemented in Sandbox on August 15, 2025 and in Production on September 15, 2025.

"Error": [
[
  {
    "Message": "Usage Limit Exceeded",
    "Detail": "Usage Limit Exceeded: To add a new account, upgrade or learn how to manage your usage limits. <br/> <a href='https://quickbooks.intuit.com/community/Help-Articles/What-are-usage-limits-in-QuickBooks-Online/m-p/228520' target=\"_blank\"><b>Learn more</b></a>",
    "code": "6570",
    "element": ""
  }
]

• The QuickBooks Online product allows chart of account types to be categorized into a few main account types, and sub-classifications for those main account types.  In the past, our Account API may have allowed incorrect account types and subtypes to be created. This resulted in incorrect categorization for ‌transactions sent via apps leveraging our APIs. We’re introducing validations to our API to match the validations that are within the QuickBooks product.

For example, the QuickBooks Online product doesn’t allow users to create a parent account with the type Fixed Asset and the subtype as AccumulatedDepreciation, AccumulatedAmortization, or AccumulatedDepletion. These can only be created as child accounts. The same validation will be added to the Account API as well. Creating a parent account with Type Fixed Asset and SubType as AccumulatedDepreciation, AccumulatedAmortization, or AccumulatedDepletion will return the following error:

{
  "Message": "A business validation error has occurred while processing your request",
  "Detail": "Business Validation Error: Fixed asset accounts (Accumulated Amortization, Depletion, or Depreciation) cannot be parent accounts.",
  "code": "6000",
  "element": "ParentRef.value"
}

This change will be implemented in Sandbox on September 15, 2025 and in Production on October 31, 2025.

4. Customer and Vendor entities: 

The “Source” field in these entities will no longer be returned in the API response. These fields will be deprecated in Sandbox on August 15, 2025 and in Production on September 15, 2025.

5. Update to Query operation:

Filtering on the ID field will not support operators >, <, >=, <=, !=, and LIKE . Only = and IN will be supported for the ID field. There is no change to filters on other fields. Taking the Accounts entity as an example:

• Select * from Accounts where ID != ‘250’ or Select * from Accounts where ID > ‘250’ will not be supported. The filter will be ignored and all values will be returned.
• Select * from Accounts where ID in (‘10’, ‘15’, ‘20’) or Select * from Accounts where ID = ‘40’ will be supported.

This change will be implemented in Sandbox on September 15, 2025 and in Production on October 31, 2025.

When will these changes be implemented? 

The following changes will be implemented in Sandbox on August 15, 2025:

• API calls to our Batch endpoint will be throttled at 120 requests per minute per realm ID
• Existing usage limits based on the product SKU will be implemented to the Chart of Accounts, Classes & Departments APIs. 
• For the CompanyInfo API, the Lat and Long fields under CompanyAddr, CustomerCommunicationAddr, and LegalAddr fields will be deprecated. 
• For Customer & Vendor API entities, the “Source” field will be deprecated. 

The following changes will be implemented in Sandbox on September 15, 2025:

• Accounting API calls will be throttled at 10 requests per second per realm ID & app
• For the CompanyInfo API, the Country field under CompanyAddr, CustomerCommunicationAddr, and LegalAddr fields will be updated to always return ISO 3-letter country codes in the API response.
• Existing product validation on Chart of Accounts type & subtypes will be implemented in the Accounts API
• For query operations, filtering on the ID field will not support certain operators. 

The following changes will be implemented in Production on September 15, 2025:

• Existing usage limits based on the product SKU will be implemented to the Chart of Accounts, Classes & Departments APIs. 
• For Customer & Vendor API entities, the “Source” field will be deprecated. 
• For the CompanyInfo API, the Lat and Long fields under CompanyAddr, CustomerCommunicationAddr, and LegalAddr fields will be deprecated. 

The following changes will be implemented in Production on October 31, 2025:

• API calls to our Batch endpoint will be throttled at 120 requests per minute per realm ID
• For the CompanyInfo API, the Country field under CompanyAddr, CustomerCommunicationAddr, and LegalAddr fields will be updated to always return ISO 3-letter country codes in the API response.
• For the CompanyInfo API, the Country field under CompanyAddr, CustomerCommunicationAddr, and LegalAddr fields will be updated to always return ISO 3-letter country codes in the API response.
• Existing product validation on Chart of Accounts type & subtypes will be implemented in the Accounts API
• For query operations, filtering on the ID field will not support certain operators. 

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. You may need to adjust your API rate of usage to remain within our throttling limits. 

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.