Quickbooks APIConnect Quickbooks without building on its API
Quickbooks has a REST API. Self-serve for any developer via the Intuit Developer portal; production QBO apps fall under the Intuit App Partner Program, where the free Builder tier gets unlimited Core (data-in) calls and 500,000 metered CorePlus (data-out) credits per month, and paid Silver/Gold/Platinum tiers get more. If you're reading the docs because you need Quickbooks to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Quickbooks and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
What the Quickbooks API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0
- Who can get access
- Self-serve for any developer via the Intuit Developer portal; production QBO apps fall under the Intuit App Partner Program, where the free Builder tier gets unlimited Core (data-in) calls and 500,000 metered CorePlus (data-out) credits per month, and paid Silver/Gold/Platinum tiers get more.
- What it covers
- Accounting entities such as customers, vendors, invoices, bills, payments, accounts, items, journal entries and financial reports.
- Limits
- 500 requests per minute per realm ID (company) and 10 concurrent requests per realm ID, and on the Builder tier CorePlus calls over the monthly credit are blocked.
Official docs: developer.intuit.com. Checked September 2026. Vendors change access terms, so confirm with Quickbooks before you build.
Building on the Quickbooks API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Quickbooks credentials, and manage tokens and refreshes. | Connect your Quickbooks account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Quickbooks task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Quickbooks work off someone's desk, the build is the slow part.
What teams usually want the Quickbooks API for
Vendor Bill Creation
Caddi reads vendor payout rows and creates matching bills with the correct vendor, expense categories, and payment terms, reducing manual bill entry for billing and finance teams.
Receipt-to-invoice reconciliation
Caddi extracts payment details from incoming receipts and matches them to the right QuickBooks invoice with the matter or client coded.
Daily payment posting
Each day, Caddi summarizes payments from LawPay or Stripe and posts the journal entries to QuickBooks with the right client coding.
Expense report posting
Caddi pulls approved Expensify reports, applies the firm's coding rules, and posts them to QuickBooks with the right matter/client.
Quickbooks API questions
Does Quickbooks have an API?
Yes. Quickbooks has a REST API, authenticated with OAuth 2.0. The official documentation is at https://developer.intuit.com/app/developer/qbo/docs/get-started.
How do I get access to the Quickbooks API?
Self-serve for any developer via the Intuit Developer portal; production QBO apps fall under the Intuit App Partner Program, where the free Builder tier gets unlimited Core (data-in) calls and 500,000 metered CorePlus (data-out) credits per month, and paid Silver/Gold/Platinum tiers get more.
Does the Quickbooks API have rate limits?
500 requests per minute per realm ID (company) and 10 concurrent requests per realm ID, and on the Builder tier CorePlus calls over the monthly credit are blocked.
Can I connect Quickbooks to my other tools without writing code against its API?
Yes. With Caddi you show the Quickbooks task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Quickbooks and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Quickbooks with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Quickbooks is reviewed before it runs in production, and every run is logged.
Connect Quickbooks without the build.
Drop your work email and pick a time. We'll show you Caddi running your Quickbooks workflow end to end.