https://github.com/conductor-is/quickbooks-desktop-node
QuickBooks Desktop API for Node.js (TypeScript or JavaScript)
https://github.com/conductor-is/quickbooks-desktop-node
javascipt nodejs qb-desktop qb-enterprise qbd qbdesktop qbdt qbe qbenterprise qbwc qbwebconnector quickbooks quickbooks-api quickbooks-desktop quickbooks-enterprise quickbooks-sync quickbooks-web-connector typescript
Last synced: 5 months ago
JSON representation
QuickBooks Desktop API for Node.js (TypeScript or JavaScript)
- Host: GitHub
- URL: https://github.com/conductor-is/quickbooks-desktop-node
- Owner: conductor-is
- License: apache-2.0
- Created: 2023-11-28T23:42:26.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2026-01-24T07:15:06.000Z (5 months ago)
- Last Synced: 2026-01-24T12:52:34.657Z (5 months ago)
- Topics: javascipt, nodejs, qb-desktop, qb-enterprise, qbd, qbdesktop, qbdt, qbe, qbenterprise, qbwc, qbwebconnector, quickbooks, quickbooks-api, quickbooks-desktop, quickbooks-enterprise, quickbooks-sync, quickbooks-web-connector, typescript
- Language: TypeScript
- Homepage: https://conductor.is
- Size: 6.08 MB
- Stars: 283
- Watchers: 2
- Forks: 12
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Security: SECURITY.md
Awesome Lists containing this project
- jimsghstars - conductor-is/quickbooks-desktop-api - QuickBooks Desktop API for Python, Node.js, TypeScript, and REST (TypeScript)
README
QuickBooks Desktop/Enterprise real-time API for Node.js, Python, and REST
Quickstart
•
Website
•
Docs
•
Examples
[Conductor](https://conductor.is) is a real-time, fully-typed API for **QuickBooks Desktop** (sometimes called QuickBooks Enterprise). In just a few lines, get real-time access to fetch, create, or update _any_ QuickBooks Desktop object type and receive a fully-typed response.
⭐ **Follow our [Quickstart guide](https://docs.conductor.is/quickstart) to get started.**
This repository contains the official Conductor **Node.js** library, which provides convenient access to our QuickBooks Desktop API from any server-side TypeScript or JavaScript application.
- For Python, see [conductor-python](https://github.com/conductor-is/quickbooks-desktop-python).
## Documentation
The REST API documentation can be found on [docs.conductor.is](https://docs.conductor.is/api-ref). The full API of this library can be found in [api.md](api.md).
## MCP Server
Use the Conductor MCP Server to enable AI assistants to interact with this API, allowing them to explore endpoints, make test requests, and use documentation to help integrate this SDK into your application.
[](https://cursor.com/en-US/install-mcp?name=conductor-node-mcp&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImNvbmR1Y3Rvci1ub2RlLW1jcCJdfQ)
[](https://vscode.stainless.com/mcp/%7B%22name%22%3A%22conductor-node-mcp%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22conductor-node-mcp%22%5D%7D)
> Note: You may need to set environment variables in your MCP client.
## Installation
```sh
npm install conductor-node
```
> [!IMPORTANT]
> If you're migrating from the old `conductor-node` package (v11 or earlier), please see the [upgrade guide](https://docs.conductor.is/qbd-api/upgrade-node).
## Key features
- **Any data type**: Query, create, or update any QuickBooks Desktop data type.
- **Real-time**: Get real-time updates on your QuickBooks Desktop data. No queues, no jobs, no cache layer -- just direct access to the data.
- **Modern API**: JSON-based REST API, replacing the old XML-based SOAP model.
- **Typed client libraries**: Fully typed libraries in Node.js and Python with autocomplete, inline docs, and type validation for endpoints, parameters, and responses.
- **Request handling**: Invisibly manages queues, timeouts, retries, and pagination.
- **Auto-pagination**: Automatically handles paginated responses to retrieve complete datasets.
- **Multi-company support**: Connects to multiple QuickBooks Desktop company files.
- **Validation**: Sanitizes and validates all inputs and outputs.
- **Unified error handling**: Streamlines error handling across the QuickBooks stack.
- **Authentication flow UI**: Simple UI for securely connecting QuickBooks Desktop accounts.
- **Dashboard**: UI to monitor and manage your QuickBooks Desktop connections and data.
- **Error resolution**: Detailed guides and instructions for resolving errors and handling edge cases.
## Usage
The full API of this library can be found with code samples at [docs.conductor.is/qbd-api](https://docs.conductor.is/api-ref).
```js
import Conductor from 'conductor-node';
const conductor = new Conductor({
apiKey: process.env['CONDUCTOR_SECRET_KEY'], // This is the default and can be omitted
});
const page = await conductor.qbd.invoices.list({ conductorEndUserId: 'YOUR_END_USER_ID' });
const invoice = page.data[0];
console.log(invoice.id);
```
### Request & Response types
This library includes TypeScript definitions for all request params and response fields. You may import and use them like so:
```ts
import Conductor from 'conductor-node';
const conductor = new Conductor({
apiKey: process.env['CONDUCTOR_SECRET_KEY'], // This is the default and can be omitted
});
const params: Conductor.Qbd.InvoiceListParams = { conductorEndUserId: 'YOUR_END_USER_ID' };
const [invoice]: [Conductor.Qbd.Invoice] = await conductor.qbd.invoices.list(params);
```
Documentation for each method, request param, and response field are available in docstrings and will appear on hover in most modern editors.
## Handling errors
When the library is unable to connect to the API,
or if the API returns a non-success status code (i.e., 4xx or 5xx response),
a subclass of `APIError` will be thrown:
```ts
const page = await conductor.qbd.invoices
.list({ conductorEndUserId: 'YOUR_END_USER_ID' })
.catch(async (err) => {
if (err instanceof Conductor.APIError) {
console.log(err.status); // 400
console.log(err.name); // BadRequestError
console.log(err.headers); // {server: 'nginx', ...}
} else {
throw err;
}
});
```
Error codes are as follows:
| Status Code | Error Type |
| ----------- | -------------------------- |
| 400 | `BadRequestError` |
| 401 | `AuthenticationError` |
| 403 | `PermissionDeniedError` |
| 404 | `NotFoundError` |
| 422 | `UnprocessableEntityError` |
| 429 | `RateLimitError` |
| >=500 | `InternalServerError` |
| N/A | `APIConnectionError` |
### Retries
Certain errors will be automatically retried 2 times by default, with a short exponential backoff.
Connection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict,
429 Rate Limit, and >=500 Internal errors will all be retried by default.
You can use the `maxRetries` option to configure or disable this:
```js
// Configure the default for all requests:
const conductor = new Conductor({
maxRetries: 0, // default is 2
});
// Or, configure per-request:
await conductor.qbd.invoices.list({ conductorEndUserId: 'YOUR_END_USER_ID' }, {
maxRetries: 5,
});
```
### Timeouts
Requests time out after 2 minutes by default. You can configure this with a `timeout` option:
```ts
// Configure the default for all requests:
const conductor = new Conductor({
timeout: 20 * 1000, // 20 seconds (default is 2 minutes)
});
// Override per-request:
await conductor.qbd.invoices.list({ conductorEndUserId: 'YOUR_END_USER_ID' }, {
timeout: 5 * 1000,
});
```
On timeout, an `APIConnectionTimeoutError` is thrown.
Note that requests which time out will be [retried twice by default](#retries).
## Auto-pagination
List methods in the Conductor API are paginated.
You can use the `for await … of` syntax to iterate through items across all pages:
```ts
async function fetchAllInvoices(params) {
const allInvoices = [];
// Automatically fetches more pages as needed.
for await (const invoice of conductor.qbd.invoices.list({
conductorEndUserId: 'YOUR_END_USER_ID',
})) {
allInvoices.push(invoice);
}
return allInvoices;
}
```
Alternatively, you can request a single page at a time:
```ts
let page = await conductor.qbd.invoices.list({ conductorEndUserId: 'YOUR_END_USER_ID' });
for (const invoice of page.data) {
console.log(invoice);
}
// Convenience methods are provided for manually paginating:
while (page.hasNextPage()) {
page = await page.getNextPage();
// ...
}
```
## Advanced Usage
### Accessing raw Response data (e.g., headers)
The "raw" `Response` returned by `fetch()` can be accessed through the `.asResponse()` method on the `APIPromise` type that all methods return.
This method returns as soon as the headers for a successful response are received and does not consume the response body, so you are free to write custom parsing or streaming logic.
You can also use the `.withResponse()` method to get the raw `Response` along with the parsed data.
Unlike `.asResponse()` this method consumes the body, returning once it is parsed.
```ts
const conductor = new Conductor();
const response = await conductor.qbd.invoices
.list({ conductorEndUserId: 'YOUR_END_USER_ID' })
.asResponse();
console.log(response.headers.get('X-My-Header'));
console.log(response.statusText); // access the underlying Response object
const { data: page, response: raw } = await conductor.qbd.invoices
.list({ conductorEndUserId: 'YOUR_END_USER_ID' })
.withResponse();
console.log(raw.headers.get('X-My-Header'));
for await (const invoice of page) {
console.log(invoice.id);
}
```
### Logging
> [!IMPORTANT]
> All log messages are intended for debugging only. The format and content of log messages
> may change between releases.
#### Log levels
The log level can be configured in two ways:
1. Via the `CONDUCTOR_LOG` environment variable
2. Using the `logLevel` client option (overrides the environment variable if set)
```ts
import Conductor from 'conductor-node';
const conductor = new Conductor({
logLevel: 'debug', // Show all log messages
});
```
Available log levels, from most to least verbose:
- `'debug'` - Show debug messages, info, warnings, and errors
- `'info'` - Show info messages, warnings, and errors
- `'warn'` - Show warnings and errors (default)
- `'error'` - Show only errors
- `'off'` - Disable all logging
At the `'debug'` level, all HTTP requests and responses are logged, including headers and bodies.
Some authentication-related headers are redacted, but sensitive data in request and response bodies
may still be visible.
#### Custom logger
By default, this library logs to `globalThis.console`. You can also provide a custom logger.
Most logging libraries are supported, including [pino](https://www.npmjs.com/package/pino), [winston](https://www.npmjs.com/package/winston), [bunyan](https://www.npmjs.com/package/bunyan), [consola](https://www.npmjs.com/package/consola), [signale](https://www.npmjs.com/package/signale), and [@std/log](https://jsr.io/@std/log). If your logger doesn't work, please open an issue.
When providing a custom logger, the `logLevel` option still controls which messages are emitted, messages
below the configured level will not be sent to your logger.
```ts
import Conductor from 'conductor-node';
import pino from 'pino';
const logger = pino();
const conductor = new Conductor({
logger: logger.child({ name: 'Conductor' }),
logLevel: 'debug', // Send all messages to pino, allowing it to filter
});
```
### Making custom/undocumented requests
This library is typed for convenient access to the documented API. If you need to access undocumented
endpoints, params, or response properties, the library can still be used.
#### Undocumented endpoints
To make requests to undocumented endpoints, you can use `conductor.get`, `conductor.post`, and other HTTP verbs.
Options on the client, such as retries, will be respected when making these requests.
```ts
await conductor.post('/some/path', {
body: { some_prop: 'foo' },
query: { some_query_arg: 'bar' },
});
```
#### Undocumented request params
To make requests using undocumented parameters, you may use `// @ts-expect-error` on the undocumented
parameter. This library doesn't validate at runtime that the request matches the type, so any extra values you
send will be sent as-is.
```ts
conductor.qbd.invoices.list({
// ...
// @ts-expect-error baz is not yet public
baz: 'undocumented option',
});
```
For requests with the `GET` verb, any extra params will be in the query, all other requests will send the
extra param in the body.
If you want to explicitly send an extra argument, you can do so with the `query`, `body`, and `headers` request
options.
#### Undocumented response properties
To access undocumented response properties, you may access the response object with `// @ts-expect-error` on
the response object, or cast the response object to the requisite type. Like the request params, we do not
validate or strip extra properties from the response from the API.
### Customizing the fetch client
By default, this library expects a global `fetch` function is defined.
If you want to use a different `fetch` function, you can either polyfill the global:
```ts
import fetch from 'my-fetch';
globalThis.fetch = fetch;
```
Or pass it to the client:
```ts
import Conductor from 'conductor-node';
import fetch from 'my-fetch';
const conductor = new Conductor({ fetch });
```
### Fetch options
If you want to set custom `fetch` options without overriding the `fetch` function, you can provide a `fetchOptions` object when instantiating the client or making a request. (Request-specific options override client options.)
```ts
import Conductor from 'conductor-node';
const conductor = new Conductor({
fetchOptions: {
// `RequestInit` options
},
});
```
#### Configuring proxies
To modify proxy behavior, you can provide custom `fetchOptions` that add runtime-specific proxy
options to requests:
**Node** [[docs](https://github.com/nodejs/undici/blob/main/docs/docs/api/ProxyAgent.md#example---proxyagent-with-fetch)]
```ts
import Conductor from 'conductor-node';
import * as undici from 'undici';
const proxyAgent = new undici.ProxyAgent('http://localhost:8888');
const conductor = new Conductor({
fetchOptions: {
dispatcher: proxyAgent,
},
});
```
**Bun** [[docs](https://bun.sh/guides/http/proxy)]
```ts
import Conductor from 'conductor-node';
const conductor = new Conductor({
fetchOptions: {
proxy: 'http://localhost:8888',
},
});
```
**Deno** [[docs](https://docs.deno.com/api/deno/~/Deno.createHttpClient)]
```ts
import Conductor from 'npm:conductor-node';
const httpClient = Deno.createHttpClient({ proxy: { url: 'http://localhost:8888' } });
const conductor = new Conductor({
fetchOptions: {
client: httpClient,
},
});
```
## Frequently Asked Questions
## Semantic versioning
This package generally follows [SemVer](https://semver.org/spec/v2.0.0.html) conventions, though certain backwards-incompatible changes may be released as minor versions:
1. Changes that only affect static types, without breaking runtime behavior.
2. Changes to library internals which are technically public but not intended or documented for external use. _(Please open a GitHub issue to let us know if you are relying on such internals.)_
3. Changes that we do not expect to impact the vast majority of users in practice.
We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.
We are keen for your feedback; please open an [issue](https://www.github.com/conductor-is/quickbooks-desktop-node/issues) with questions, bugs, or suggestions.
## Requirements
TypeScript >= 4.9 is supported.
The following runtimes are supported:
- Web browsers (Up-to-date Chrome, Firefox, Safari, Edge, and more)
- Node.js 20 LTS or later ([non-EOL](https://endoflife.date/nodejs)) versions.
- Deno v1.28.0 or higher.
- Bun 1.0 or later.
- Cloudflare Workers.
- Vercel Edge Runtime.
- Jest 28 or greater with the `"node"` environment (`"jsdom"` is not supported at this time).
- Nitro v2.6 or greater.
Note that React Native is not supported at this time.
If you are interested in other runtime environments, please open or upvote an issue on GitHub.
## Contributing
See [the contributing documentation](./CONTRIBUTING.md).