Quickstart

TenkeyBridge exposes QuickBooks Desktop (and Enterprise) through the same REST shape as the QuickBooks Online Accounting API. If you already have a working QBO integration, you don't rewrite it — you point it at TenkeyBridge.

Early development

TenkeyBridge is in early development. The hosted gateway at api.tenkeybridge.com is not live yet — this documentation describes the compatibility contract we build and test against, and it will be the contract the hosted service ships with.

The only required change

Same OAuth 2.0 flow, same paths, same JSON entities. Swap the base URL:

- const BASE = "https://quickbooks.api.intuit.com";
+ const BASE = "https://api.tenkeybridge.com";

Everything else stays:

// Unchanged from your existing QBO code
const res = await fetch(
  `${BASE}/v3/company/${realmId}/invoice/${id}`,
  { headers: { Authorization: `Bearer ${accessToken}` } }
);
const invoice = await res.json();

That's it for the happy path.

What to expect

Reads come back essentially unchanged — the compatibility matrix marks almost every entity's read side Full. Writes are where Desktop's quirks surface: line-item shapes, tax handling, and a handful of fields need a quick, documented change before they behave identically to QBO.

When you hit a case Desktop genuinely can't do, you get a QBO-style Fault back with a stable, versioned error code instead of a silent difference — see Error codes for the full list and what to do about each one.

Before you integrate a new entity, check the compatibility page for its field-by-field support and the exact fix for anything marked partial.