Top 5 QuickBooks Online API Limitations to Know Before Developing a QBO App

January 18, 2026 5 min read
Diagram depicting QuickBooks API limitations, featuring a computer screen, smartphone, and the QuickBooks logo intricately connected by gears and lines.

Introduction

When listing a QuickBooks Online (QBO) app in the app store, you should be aware of several limitations to avoid potential setbacks.

Before starting QuickBooks app development, it’s critical to understand how these constraints affect integrations, automation, and scalability.

When listing a QuickBooks Online (QBO) app in the App Store, developers must be aware of several API limitations to avoid unexpected roadblocks during development or approval.

Below are the five most critical QuickBooks API limitations and possible workarounds.

1. Tag Support Limitations in QuickBooks API

Limited Functionality

  • The QuickBooks Online API has limited support for managing tags. While you can retrieve and list tags, you cannot create, update, or delete tags via the API.
  • This limitation can impact how you categorize and organize transactions programmatically.

Source: Intuit Developer Hub QuickBooks Online API Best Practices​ (https://help.developer.intuit.com/s/article/QuickBooks-Online-API-Best-Practices)

Usage in Reports

  • Tags in QBO can be useful for generating reports within the QuickBooks interface.
  • However, the API does not fully support querying tags across all report types, limiting the ability to create comprehensive reports programmatically.

Source: Intuit Developer Platform Throttling Limit (https://help.developer.intuit.com/s/article/Platform-Throttling-limit)

I have written a detailed guide on a workaround to overcome this limitation: No Tags in QuickBooks Online API? 3 hacks to work around it!

2. Custom Field Limitations in QuickBooks Online API

Read-Only Access

  • While you can retrieve custom fields, updating or creating custom fields via the QBO API is not fully supported.
  • This means that any customization done within the QBO interface needs to be manually mirrored if it’s to be used programmatically​.

Source: Intuit Developer Platform Throttling Limit​ (https://help.developer.intuit.com/s/article/QuickBooks-Online-API-Best-Practices)

Screenshot of the Intuit Developer website displaying a table highlighting QuickBooks API limitations. It indicates that while creating custom field names is supported through the UI, it is not possible via the API.

Field Type Restrictions

  • Custom fields in QuickBooks Online have specific data types, such as text, number, and date.
  • However, the API may not support all operations for each type, which can limit how custom data is handled and manipulated in your application.
  • With QuickBooks Online Advanced, customers can now create up to 10 custom fields with various data types.
  • To retain compatibility with an app using custom fields, the first three String custom fields in QuickBooks Online Advanced will be available through the existing API functions outlined here.

Source: Enhanced Custom Fields for QuickBooks Online Advanced (https://help.developer.intuit.com/s/article/Enhanced-Custom-Fields-for-QuickBooks-Online-Advanced)

3. Bill Payment API Limitations in QuickBooks Online

The QuickBooks Online API has specific limitations when it comes to returning certain fields in bill payments. Notably, the API does not return the following fields:

  • Approval Status: This field indicates whether a bill payment has been approved.
  • Tags: These are used to categorize transactions within QuickBooks.
  • Payment Method: This field specifies how the payment was made (e.g., credit card, bank transfer).
  • Attachments Confirmation: Indicates whether any attachments are associated with the bill payment.

These limitations can impact how you manage and report on bill payments in your QuickBooks Online integrations.

To resolve these limitations, the article from Satva Solutions suggests using a Robotic Process Automation (RPA) Solution with Microsoft Power Automate.

This approach automates the retrieval of these fields directly from the QuickBooks Online interface and stores them in an SQL database.

By doing RPA, you can overcome the API limitations and make certain that all necessary information is captured and accessible for your application.

For more information on solving this limitation, you can read my full article Solving QuickBooks Online API Limitations with RPA

4. Bank Feed API Limitations in QuickBooks Online

The most common questions I encounter when working with accountants and CPAs are for their Accounting automation projects.

Does QuickBooks have an API for downloading bank statements or transactions?

When I asked ChatGPT’s latest model the same question, I found the answer wrong.

Screenshot showing text about QuickBooks API access, highlighting its limitations: it permits access to bank transactions via bank feeds but doesn't support direct downloading of full bank statements.

Additionally, ChatGPT was hallucinating about having an endpoint to access bank transactions; check the answer below from ChatGPT.

You’re absolutely right! QuickBooks Online (QBO) does not provide a “banktransactions” endpoint (i.e.,/v3/company/{company_id}/banktransactions )in its official API documentation.

The screenshot displays API usage instructions for accessing transactions, focusing on two endpoints: `/v3/company/{company_id}/query` and `/v3/company/{company_id}/banktransactions`. It also touches on QuickBooks API limitations, highlighting constraints in transaction retrieval.

The QuickBooks Online (QBO) API allows access to bank transactions that have been added or matched within QuickBooks.

These transactions can be queried like any other transaction type, such as expenses, checks, or deposits.

However, transactions in the “For Review” status that are imported via bank feeds but not yet categorized or matched are not accessible through the API.
A transaction review table with columns for date, description, amount, and assign to helps navigate QuickBooks API limitations. Buttons for confirm and review are conveniently on the right side.

Bank Feed line items which are not yet categorized, NOT available for download via API

Technical Perspective:

Due to economic and security constraints, QuickBooks Online will not provide an API endpoint for retrieving original bank statement line items.

The platform relies on third-party paid services like Plaid and Yodlee for bank statement retrieval, which incur per-access costs.

Exposing a direct API could enable potential misuse, such as programmatically accessing multiple bank accounts without substantial financial compensation to these data providers.

Key risks of an open API include:

  • Unauthorized mass bank statement extraction
  • Circumvention of service provider payment structures
  • Potential data privacy and security vulnerabilities

The current approach protects QuickBooks Online’s financial interests and data integration partnerships.

5) Projects API Limitations in QuickBooks Online

Project-wise tracking is disabled in QuickBooks Online, though it can be very powerful for some industries, such as:

  • Construction companies
  • Architecture firms
  • Professional services businesses
  • Consulting firms
  • Marketing and creative agencies

By default, project financial tracking is disabled in QuickBooks Online. You need to go to advanced settings and enable it.

Screenshot of QuickBooks settings page showing the "Projects" option highlighted, with a toggle to enable or disable project financial tracking, and buttons to cancel or save changes. Be mindful of QuickBooks API limitations when integrating this feature for seamless financial management.

It shows a way to enable project-wise tracking of income, expense, and time.

Once enabled, QuickBooks lets you see all your sales, expenses, and timesheets by project.

The project dashboard, compatible with QuickBooks API, reveals a profit margin of 56%, reflecting $4,000 income against $1,750 for cost of goods sold, resulting in a $2,250 profit. It also features sections for expenses, bills, and payroll hours.

A summary view of project profitability, cost, and expenses.

However, QuickBooks has no Direct API for adding, editing, updating, and deleting projects.

Limitations

No Dedicated Project Entity

QuickBooks uses a special flag (IsProject) to manage projects as sub-customers. This may not offer the same granularity as a dedicated project entity.

Limited Advanced Feature

Advanced project features, like profitability tracking or time tracking, are not directly accessible through the API.

Best Practices for Working Around QuickBooks API Limitations

  • Efficient Error Handling: Given the various limitations and potential for incomplete data, executing robust error handling and logging mechanisms is essential.
  • Use of Webhooks: To keep data synchronized and up-to-date, leveraging QBO webhooks can provide instant updates and reduce the necessity of frequent polling, which is subject to rate limits (Intuit Developer Hub)
  • Referring Documentation: Regularly referring to the QuickBooks Online API Documentation for updates and best practices can help mitigate some of these limitations.
  • Change Data Capture CDD: Use change data capture to see which API entities and what data changed within a certain timeframe. The maximum number of queries you can query for changes up to the past 30 days.

Source: Change Data Capture QuickBooks Online API (https://developer.intuit.com/app/developer/qbo/docs/learn/explore-the-quickbooks-online-api/change-data-capture)

Knowing these limitations will help you design more resilient and efficient integrations with QuickBooks Online, ensuring your application can effectively handle the API’s quirks and constraints.

These API limitations can create challenges for tools that rely on frequent transaction syncing or reconciliation workflows. As accounting platforms evolve, AI systems are starting to improve how financial data is analyzed and matched across systems. We explain this shift in detail in our guide on how AI is transforming financial reconciliation.

Conclusion

QuickBooks Online may remove some of these restrictions in the future.

Always refer to the latest Intuit QuickBooks Online API documentation.

Monitor developer announcements for changes in QBO API rate limits and entity behavior.

If you’re looking for a Custom QuickBooks integration service or need help navigating API challenges, contact Satva Solutions today!

Chintan Prajapati
Article by

Chintan Prajapati

Chintan Prajapati, a seasoned computer engineer with over 20 years in the software industry, is the Founder and CEO of Satva Solutions. His expertise lies in Accounting & ERP Integrations, RPA, and developing technology solutions around leading ERP and accounting software, focusing on using Responsible AI and ML in fintech solutions. Chintan holds a BE in Computer Engineering and is a Microsoft Certified Professional, Microsoft Certified Technology Specialist, Certified Azure Solution Developer, Certified Intuit Developer, Certified QuickBooks ProAdvisor and Xero Developer.Throughout his career, Chintan has significantly impacted the accounting industry by consulting and delivering integrations and automation solutions that have saved thousands of man-hours. He aims to provide readers with insightful, practical advice on leveraging technology for business efficiency.Outside of his professional work, Chintan enjoys trekking and bird-watching. Guided by the philosophy, "Deliver the highest value to clients". Chintan continues to drive innovation and excellence in digital transformation strategies from his base in Ahmedabad, India.