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 access

TenkeyBridge is in early access. The hosted gateway at api.tenkeybridge.com is live. There is no self-serve signup yet — credentials are issued manually during onboarding (see Authentication) until the developer portal ships.

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.

Updates work the way you'd expect from QBO: POST the entity with Id and SyncToken, optionally with ?operation=update on the URL (both are accepted, and a body with Id is always routed as an update — it never falls through to create). One semantic difference to know: Desktop has no partial-update mode, so every update behaves like QBO's sparse update — fields you omit from the body are left alone, never cleared, even on a full-body update with no sparse flag set.

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 entity matrix for its field-by-field support and the exact fix for anything marked partial. Cross-cutting rules for IDs, SyncToken, sparse updates, and query support live in IDs, SyncToken & sparse updates.

Where to go next

1. Authentication — OAuth 2.0 code flow (same as QBO).
2. Node.js client — @tenkeybridge/client, typed helpers + token management for new code.
3. Edge agent install — Windows agent next to QuickBooks.
4. Entity matrix — full live / planned / gap coverage.
5. Gateway ops — deploy, migrate, and seed (operators).