TenkeyBridge

BLOG

Notes from the bridge

Field notes on putting a QuickBooks Online–compatible API in front of QuickBooks Desktop and Enterprise: sync, errors, hosting, and the sandbox.

Isometric illustration of an open bank-statement ledger with green check marks in a column of tick boxes and a pen across the page.

Marking QuickBooks Desktop Transactions Cleared Over a REST API

How to set and read cleared status on QuickBooks Desktop transactions over REST: per-split semantics, which types work, and why the read-back needs a GL report.

Read more
Isometric illustration of a brick firewall with an arched gateway, a paper airplane passing through, padlock and shield on top.

A New Hostname, a Hosted Desktop, and a Firewall That Said No

A September 2026 hosted QuickBooks cutover failed twice: a Let's Encrypt chain the desktop wouldn't validate, and a FortiGate that blocked an unrated hostname.

Read more
Isometric illustration of an open shipping crate with a ledger, gear, coin, bar chart and check mark floating out

TenkeyBridge Changelog, October 2026: 84 Reports, Cleared Status, Multicurrency, and More Writes

What shipped in the QuickBooks Desktop API in October 2026: 84 reports, cleared status, multicurrency, Desktop-only voids, Projects as jobs, and new npm clients.

Read more
Isometric illustration of a card-catalog cabinet with three open drawers and small green chart cards rising out

84 QuickBooks Desktop Reports Over One REST API: A Field Guide

A tour of the 84 reports TenkeyBridge exposes from QuickBooks Desktop over a QBO-shaped REST API: groups, params, five sample GETs, and the edges that bite.

Read more
A paper invoice stamped in red ink on a cluttered desk beside a keyboard, a hand resting on its edge

Void vs. Delete in QuickBooks Desktop via API: What Each One Leaves Behind

Void keeps the transaction with zeroed amounts and a VOID: memo; delete erases it. How operation=void works on Desktop, which types support it, and the payment exception.

Read more
Isometric illustration of a balance scale weighing a sliver of a coin against a stack of whole coins.

Why a $0.0725 Rate Came Back as $0.07: Sub-Cent Prices on QuickBooks Desktop

A lab-testing integration billed fractions of a cent per unit and QuickBooks rewrote the amount. Here's the price-vs-amount distinction and the gateway v126 fix.

Read more
Developer seen from behind at a dark desk, reading HTTP error responses scrolling in a terminal window.

503 vs. 504 from QuickBooks Desktop: Which Requests Are Safe to Retry

503 AGENT_OFFLINE means the request never reached QuickBooks. 504 AGENT_TIMEOUT means it may have applied. Here's a retry policy that respects the difference.

Read more
Hands at a laptop loading a .QWC file into Web Connector, with raw qbXML open on a second monitor.

QuickBooks SDK vs. Web Connector vs. a REST Bridge: Picking a Desktop Integration Path

Three ways to reach QuickBooks Desktop: raw qbXML over the COM SDK, a SOAP Web Connector service, or a QBO-shaped REST API. Who hosts what, and what breaks.

Read more
Developer seen from behind at a lamp-lit desk reading a JSON invoice error response on a laptop screen.

Syncing Invoices to QuickBooks Desktop Over a REST API

Create and update QuickBooks Desktop invoices with QBO-style JSON: CustomerRef, line items, tax codes, the 11-character DocNumber limit, and SyncToken handling.

Read more
Developer at a desk reviewing a JSON batch response on screen with several faulted items highlighted.

QuickBooks Batch Requests Are Not Transactions: Handling Partial Failure on Desktop

A QuickBooks batch is not atomic. How to read per-item results by bId, why structural errors reject the whole request, and how to retry only the failed items.

Read more
Developer seen from behind at a desk at night reading a JSON API response on a monitor

Change Data Capture Against QuickBooks Desktop: The 30-Day Window, the 1,000-Object Cap, and the Deactivation Gotcha

How /cdc behaves against a QuickBooks Desktop company file: the 30-day changedSince limit, CDC_OVERFLOW faults, per-entity isolation, and why deactivation isn't a delete.

Read more
Developer seen from behind editing an MCP server JSON config on a laptop beside a chat window at night

A QuickBooks MCP Server for Desktop: Giving an AI Agent Safe, Checkable Access

Run @tenkeybridge/mcp over npx to give Claude or any MCP client five QuickBooks Desktop tools, a compatibility catalog, and errors agents can actually fix.

Read more
Person seen from behind configuring a Web Connector poll interval inside a remote desktop session on a monitor.

Hosted QuickBooks on Rightworks: Connecting Without Installing Anything

Hosted QuickBooks Desktop blocks agent installs. Here's how to reach it over the Web Connector that's already on the machine — four steps, no inbound firewall rules.

Read more
Developer seen from behind comparing two JSON API responses in split browser windows on a desk monitor.

QBO Sandbox vs. TenkeyBridge Sandbox: The Same Request, Side by Side

Run the same QuickBooks API request against Intuit's QBO sandbox and a Desktop-backed sandbox, diff the responses, and see where Desktop semantics actually differ.

Read more
Developer seen from behind at a desk, laptop showing JSON API responses beside a notebook of handwritten record IDs.

Build Against QuickBooks Desktop Without Installing QuickBooks

Every TenkeyBridge org gets a free QuickBooks Desktop sandbox: a hosted realm that answers the /v3 API with seeded data, fixed record IDs, and on-demand resets.

Read more
View over a bookkeeper's shoulder of an invoice on one monitor and JSON code on another

Sparse Updates vs. Full Replacement: Syncing Invoices to QuickBooks Desktop Without Clobbering Edits

How QBO's sparse update semantics map onto QuickBooks Desktop's EditSequence, why SyncToken conflicts happen, and how to write a sync loop that's actually idempotent.

Read more
Technician kneeling at a server rack in a small closet, working on a Windows Server console screen.

Integrating with Multi-User and Hosted QuickBooks Desktop (RDS, Right Networks, Citrix)

How sessions, file modes, integrity levels, and Windows service accounts change when QuickBooks Desktop lives on a server or a hosting provider — and what actually works.

Read more
Developer at a back-office desk facing an old PC running QuickBooks Desktop with an error dialog on screen

Decoding QuickBooks Desktop Errors: qbXML Status Codes, HRESULTs, and QBO-Style Faults

A field guide to QuickBooks Desktop error codes — qbXML statusCode 3140, COM HRESULTs like 0x80040408 — and how they map onto QuickBooks Online-style faults.

Read more
Developer at a desk with two monitors showing API logs and code, with a handwritten checklist taped to the screen.

The Checklist for Pointing Your QuickBooks Online Integration at Desktop

A practical, step-by-step checklist for developers adapting a working QBO integration to support QuickBooks Desktop and Enterprise via a compatible REST API.

Read more

Point your QuickBooks Online integration at QuickBooks Desktop

Point your QuickBooks Online integration at QuickBooks Desktop

The whole migration is a base URL. Here's the full walkthrough — token, query, and invoice write — against a real Desktop company file.

Read more

QuickBooks Desktop errors don't have to be cryptic

QuickBooks Desktop errors don't have to be cryptic

How TenkeyBridge turns Desktop's 3140s and 0x8004-somethings into QBO faults with causes, fixes, and a docs link on every error.

Read more