Source connector

QuickBooks connector

QuickBooks integration for databases, warehouses and BI tools

SMB accounting for invoices, expenses, and ledger activity. Datrise captures QuickBooks entities such as customers, invoices, bills, payments, and chart-of-accounts entries, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The QuickBooks Online Accounting API v3 (minorversion 75) authenticates with OAuth 2.0, incremental runs key on MetaData.LastUpdatedTime, or the CDC endpoint's changedSince parameter, and QuickBooks caps calls at 500 requests per minute per realm (company) with a 10-concurrent-request cap; the Batch endpoint is throttled separately at roughly 120 requests per minute per realm.

Of the 5 objects, 3 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `quickbooks_customers`) with a schema derived from the QuickBooks API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the QuickBooks pipeline page, and join the waitlist to get the QuickBooks connector (ERP) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What QuickBooks data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
customers	quickbooks_customers	Upsert by primary key, incremental on updated-at
invoices	quickbooks_invoices	Append-only, incremental by timestamp
bills	quickbooks_bills	Upsert by primary key, incremental on updated-at
payments	quickbooks_payments	Append-only, incremental by timestamp
chart-of-accounts entries	quickbooks_chart_of_accounts_entries	Upsert by primary key, incremental on updated-at

QuickBooks API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	QuickBooks Online Accounting API v3 (minorversion 75)
Authentication	OAuth 2.0 — OAuth 2.0 authorization-code grant only; access tokens last 1 hour and refresh tokens last up to 100 days, rotating on each refresh call.
Pagination	offset — The query language pages results with `STARTPOSITION` and `MAXRESULTS` (1-based row offset); `MAXRESULTS` defaults to 100 and is capped at 1000 rows per query.
Rate limit	500 requests per minute per realm (company) with a 10-concurrent-request cap; the Batch endpoint is throttled separately at roughly 120 requests per minute per realm
Incremental cursor	MetaData.LastUpdatedTime, or the CDC endpoint's changedSince parameter — The CDC endpoint's practical lookback window is documented as up to 30 days; syncs that lapse longer must fall back to a full query re-sync.
Webhooks	Yes — Intuit webhooks (Create/Update/Delete/Merge/Void notifications)
Bulk export	Yes — Batch API (up to 30 operations per request)
Deletes detectable	Yes — The CDC endpoint reports entities with status Deleted/Voided/Merged since changedSince; a plain Query silently omits deleted records

Official API reference

What bites when replicating QuickBooks

Minor versions 1-74 were deprecated August 1, 2025; a request omitting `minorversion` or specifying an old one is silently served as version 75, which can change payload shape.
The Batch endpoint caps requests at 30 combined operations and is throttled separately at roughly 120 requests per minute per realm, distinct from the general 500-per-minute limit.
The CDC endpoint's response is capped at 1000 objects and its practical change-lookback window is documented at 30 days; heavier change volume needs shorter query windows or more frequent polling.
Refresh tokens are valid up to 100 days and rotate on every refresh call; failing to persist the newest refresh token from each response can lock the integration out and force re-consent.

Compare this against every other documented API

Popular destinations for QuickBooks

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

QuickBooks connector FAQ

What QuickBooks data does the connector extract?: 5 objects: customers, invoices, bills, payments and chart-of-accounts entries. Each lands in its own table with types preserved; history-style objects (2: invoices and payments) load as append-only streams.
Is the QuickBooks integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load QuickBooks data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each QuickBooks → destination pair has its own page with the object-to-table mapping.

Related ERP sources

Other sources in the same category, each with its own connector page.

Early access

Launch your QuickBooks pipeline with guided onboarding

Join the waitlist to get priority access for QuickBooks integrations with guided setup, schema-aware mapping, and production-grade incremental sync.