The API Report CardAPI Index
THE API REPORT CARD / Construction / QuickBooks for Contractors
QuickBooks for Contractors

QuickBooks for Contractors API

quickbooks.intuit.com

Contractor Edition runs on the legacy QuickBooks Desktop SDK: qbXML via local COM or the Windows-only Web Connector, about 150 request types. The SDK is free with no review, but there is no REST, OAuth, webhooks, or sandbox, and Intuit no longer sells new Premier Contractor plans.

Last verified: July 2026Construction
API GRADE
A+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA real but legacy surface: the QuickBooks Desktop SDK speaks qbXML over COM or the SOAP Web Connector.
AccessGOODThe Desktop SDK is free with no app review; docs are public at developer.intuit.com.
CoverageGOODAbout 150 request types: jobs, estimates, invoices, time tracking, payroll items, and job-cost data.
AuthPOORAuth is a per-machine .QWC file with a locally stored user-set password; no OAuth, no cloud auth, no portable token.
Docs & DXGOODSDK reference and programmer guides are public; testing means a local QuickBooks install, and there are no webhooks.
StabilityPOORNew Contractor Edition sales ended in 2024 and live desktop services are sunsetting, while qbXML schemas drift across year versions.
Supergood: QuickBooks for Contractors shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

QuickBooks for Contractors scores A+ on the API Report Card. Contractor Edition runs on the legacy QuickBooks Desktop SDK: qbXML via local COM or the Windows-only Web Connector, about 150 request types. The SDK is free with no review, but there is no REST, OAuth, webhooks, or sandbox, and Intuit no longer sells new Premier Contractor plans.

Tried to integrate with QuickBooks for Contractors?
SOURCES
No native REST API and no JSON, every Contractor Edition integration must speak XML SOAP via qbXML over the QuickBooks Web Connector, a Windows-only utility apideck.com β†—
No OAuth, no cloud auth, no user-portable token, authentication is a customer-installed .QWC config file with username and a user-set password tied to a single PC static.developer.intuit.com β†—
No native webhooks, change detection (new jobs, new estimates, new change orders, posted bills, paid invoices) requires QBWC polling on a 1-60-minute interval, so 'real-time' job-cost updates are impossible without a unification-layer middleware help.developer.intuit.com β†—
QBWC polling architecture means the integration only runs when QuickBooks is open and QBWC is running on the contractor's office PC, laptops that go to sleep or close QuickBooks at 5pm break the sync, and weekend job-cost updates lag until Monday techfrolic.com β†—
No managed sandbox, developers must connect to a test Contractor Edition company file on a local QuickBooks install they buy and maintain themselves; cloud-based CI/CD against QBD Contractor is essentially impossible developer.intuit.com β†—
qbXML schema differs between QuickBooks year-versions and editions (Pro vs Premier Contractor vs Enterprise Contractor vs Mac), developers must maintain version-specific request shapes and feature-detect at runtime, particularly for Customer:Job hierarchies and Estimate revisions developer.intuit.com β†—
Customer:Job parent-child hierarchy requires special-case handling, jobs are modeled as Customers with a ParentRef, and integrations that flatten the model lose the job-costing dimensionality developer.intuit.com β†—
Change Orders are not a first-class object, they're modeled as Estimate revisions (a new line item on the original Estimate with the change-order description), forcing integrations to diff estimate versions to detect change-order activity contractortoolstack.com β†—
QBWC error handling is opaque, failed requests surface as cryptic numeric error codes that the developer must decode against the SDK reference; many errors require restarting QBWC or the QuickBooks app to recover, breaking unattended overnight syncs static.developer.intuit.com β†—
Large job-cost queries (Job Estimates vs. Actuals across years of jobs, full TimeTracking history across crews) are slow and can lock multi-user Contractor company files, pulling years of transactions over QBWC can take hours and can block office staff from working in QB rollout.com β†—
Intuit Hosting/Right Networks Citrix sessions (used heavily by Enterprise Contractor customers for remote field-trailer access) add another layer of indirection, QBWC runs inside the hosted session, the developer's SOAP endpoint must be reachable from the hosting provider's network, and firewall/NAT/AD-domain config becomes a per-customer support burden gotomyerp.com β†—
No path to webhooks or push notifications without paying a unification layer (Conductor, Rutter, Codat, Apideck, Merge.dev), every Contractor Edition integrator either rebuilds the same QBXML/QBWC plumbing or pays for the middleware conductor.is β†—
End-of-support dates wipe out integration reliability, Premier Plus Contractor on QBD 2023 loses bank feeds, payroll, and security patches May 31, 2026; QBD 2024 hits the same wall in September 2027, breaking any integration that depends on those services clonepartner.com β†—
Intuit invests essentially zero in modernizing the Contractor Edition integration surface, the documented strategy is to migrate contractors to QBO (where the job-costing model is weaker) or to abandon them to Sage/Foundation, leaving the QBD Contractor SDK frozen on its early-2000s architecture help.developer.intuit.com β†—
Intuit stopped selling new Pro Plus, Premier Plus (including Contractor Edition), and Mac Plus subscriptions to U.S. customers on September 30, 2024, existing subscribers can renew, but no new buyers can purchase Premier Plus Contractor method.me β†—
QuickBooks Desktop 2023 loses all live services May 31, 2026, payroll tax tables freeze, bank feeds disconnect, security patches stop, forcing contractors to upgrade to Enterprise or migrate clonepartner.com β†—
QuickBooks Desktop 2024 is the LAST new release for non-Enterprise SKUs; once its support ends in September 2027 every Premier Contractor customer is on unsupported software method.me β†—
Effective February 1, 2026 Enterprise prices increased materially, Silver 1-user from $1,703 to $1,873/yr, Gold/Platinum/Diamond tiers all increased, outpacing inflation and driving a contractor exodus bradymartz.com β†—
New per-employee Enhanced Payroll fee on Enterprise Gold and Platinum (billed monthly per unique employee paid, per company file), a material new cost for contractors with large field crews kempercpa.com β†—
Job costing requires meticulous manual setup, every transaction must be tagged to a Customer:Job and items must be carefully cost-coded for the Job Estimates vs. Actuals report to be accurate; one missed assignment skews the report contractortoolstack.com β†—
Credit card and bank-feed expense categorization is a known trap, feed transactions default to the bank GL account with no Customer:Job, leaving expenses invisible to job-cost reports until manually re-coded contractortoolstack.com β†—
AIA G702/G703 progress billing is NOT natively supported in a clean form, contractors either rebuild templates manually, use third-party add-ons, or upgrade to Sage 100 Contractor / Foundation foundationsoft.com β†—
The mobile/field experience is essentially absent, QuickBooks Desktop is a thick Windows client; the QuickBooks Time mobile app is the only field-facing surface and it does not give field crews access to job-cost reports, change orders, or POs contractortoolstack.com β†—
Multi-user mode performance degrades on large company files (10+ years of job history), condense-data operations become a chronic operational burden for established contractors quickbooks.intuit.com β†—
Intuit customer support has visibly declined, long hold times, script-reading offshore first-tier reps, and unresolved account-management issues are the #1 complaint across G2, Capterra, BBB, and Reddit bbb.org β†—
Windows 11 compatibility issues with older QBD Contractor versions have left contractors stuck on aging hardware or paying for hosted Right Networks/AceCloud Citrix sessions bbb.org β†—
'Done-for-You' AI feature investment is concentrated on QBO and Intuit Enterprise Suite, Contractor Edition (and Desktop generally) receives essentially no new feature investment, only the bare minimum to keep payroll/tax/bank-feed services running until sunset bradymartz.com β†—
Migration off Contractor Edition to QBO Plus/Advanced is operationally painful, job costing in QBO is materially weaker (no Customer:Job hierarchy in the same form, no native Estimates-to-Sales-Orders flow, no Contractor-edition reports), forcing contractors into Sage 100 Contractor, Foundation, or Sage Intacct Construction instead premiercs.com β†—