Modern REST API for
nXus creates a cleaner path out of QBXML with a typed REST API, generated SDKs, and a developer experience that feels built for current tools instead of legacy connectors.
nXus lets your application work with QuickBooks Desktop through a modern JSON REST interface while translation to QBXML happens behind the scenes.
Connect modern web apps, SaaS tools, and internal platforms to QuickBooks Desktop with JSON over HTTP instead of handling QBXML directly.
Use nXus as a bridge while moving workflows and data from QuickBooks Desktop into QuickBooks Online or other cloud systems.
Keep current products useful longer by making communication between QuickBooks Desktop and newer services much easier to maintain.
import { NxusClient, NxusApiError, type Customer, type PaginatedPage } from '@nxus/sdk';
const nxus = new NxusClient({ apiKey: process.env.NXUS_API_KEY });
try {
const result: PaginatedPage<Customer> = await nxus.customers.list({
connectionId: 'conn_abc123',
limit: 50
});
console.log(result.data);
} catch (err) {
if (err instanceof NxusApiError) {
console.error(`API Error: ${err.userMessage}`);
console.log(err.validationErrors);
}
}Input
JSON REST
Translation
Live Mapping
Output
Structured JSON
From first API call to live production traffic, nXus keeps the path short. Here are the three steps teams follow to evaluate, connect, and go live.
Step 1
Teams usually begin in the interactive API reference to inspect schemas, validate request shapes, and compare code samples before they wire nXus into a live product. The goal is to let you learn the surface area in browser first, then move into your SDK or app with fewer unknowns.
Step 2
When you're ready to connect QuickBooks Desktop, nXus creates a guided setup flow for a specific company file. That hosted wizard walks the operator through authentication, QuickBooks Web Connector setup, and the permissions needed to keep the integration attached to the right desktop environment.
Step 3
After setup, your application sends ordinary JSON REST requests while nXus handles the QuickBooks translation layer behind the scenes. Billing is tied to the company file connection, paid access is enabled from the dashboard, and subscribed tenants manage invoices, payment methods, and cancellations through the billing portal.
nXus returns structured, readable error responses so your app can guide operators toward the right fix instead of dropping them into generic failures.
Applications can inspect the same predictable error shape instead of special-casing every endpoint.
User-facing text stays understandable for operators while still preserving the technical context developers need.
The most common failures map cleanly to concrete fixes like rotating a key, reopening QuickBooks, or correcting a payload.
{
"error": {
"code": "api_key_invalid",
"type": "authentication_error",
"message": "The provided API key is invalid or has been revoked.",
"userFacingMessage": "Your API key is no longer valid. Create or rotate a key and try again.",
"httpStatusCode": 401
}
}The API key is missing, invalid, expired, or revoked.
Recommended fix: Confirm the Bearer token, verify the environment, and rotate the key if needed.
Retry guidance: Retry only after updating credentials.
View full error docsWe've handled the complexities of the QuickBooks Web Connector so you don't have to. Build features, not infrastructure.
Fully typed REST endpoints with OpenAPI specification
Enterprise-grade security with API keys, JWT auth, and TLS 1.2+ encryption.
Full CRUD support for Invoices, Customers, Vendors, Projects, and complex multi-currency reports.
Browse every endpoint, schema, and code sample in a live API reference before you write production code.
Generate a hosted setup flow for each company file so the QuickBooks Web Connector install is guided instead of manual guesswork.
Live requests flow through nXus without persisting production data. Client controls stay centralized in the portal, while secure billing is handled directly by Stripe.
Stop maintaining brittle COM automation. There's a better way.
Choose monthly or annual billing. Annual plans reflect 2 months free in the first year, and duplicate connections to the same QuickBooks company file are not billed twice. Paid checkout starts from the dashboard, and subscribed clients manage invoices, cards, and cancellations in the billing portal.
For prototypes, sandbox integrations, and early validation.
No card required while you validate your integration.
For live company files that need predictable production access.
Introductory pricing for early customers who want to lock in a lower annual rate.
Pricing is per connection, billed once per company file. If multiple connections point to the same QuickBooks file, that file is only billed once.
A QuickBooks sample file can be used for development and testing. Testing data may be cached for analysis and is not treated as secure storage, so sample data only.
Production traffic currently runs as a pass-through. No production data persists on nXus servers and the server does not retain knowledge of that data after the request completes.