Conductor Docs

Documentation

Help

Have any questions?

Community

The key concepts you must know to use Conductor.

Terminology

The best QuickBooks Desktop integration on the planet.

Get started with Conductor

Create your first EndUser and connect to QuickBooks Desktop in 5 minutes.

Quickstart

Fundamentals & FAQ

Enable your users to securely connect their QuickBooks Desktop to your application.

Authentication flow

Use API keys to authenticate API requests.

API keys

Check an EndUser's connection status

Catch and respond to connection errors, invalid requests, data problems, and more.

Error handling

Use Conductor's built-in autocomplete to discover all available APIs, requests parameters, and response fields.

Autocomplete

Execute real-time requests for *any* QuickBooks Desktop object type with fully-typed requests and responses.

Node.js / TypeScript for QuickBooks Desktop

If your backend does not use Node.js, you can use the REST API to interface with QuickBooks Desktop directly.

REST API for QuickBooks Desktop

Create your own QuickBooks Desktop test instance with an AWS WorkSpace.

Create a QuickBooks Desktop test instance

Pointers to help you create the best QuickBooks Desktop integration for your users.

QuickBooks Desktop integration tips

Understanding the relationship between customers and jobs in QuickBooks Desktop.

Jobs and customers

Vendors

Invoices

Sales receipts

Bills

Inventory items

Conductor supports read, create, and update for *every* QuickBooks Desktop object type.

Request more examples!

Authentication

Request IDs

The ConductorError object

An EndUser represents a user of your application. Use it to connect integrations.

The EndUser object

Create an EndUser

Retrieve an EndUser

List all EndUsers

Checks whether the specified IntegrationConnection can connect and process requests end-to-end.

Ping an EndUser's connection

This object represents a connection between an end-user and a third-party platform.

The IntegrationConnection object

Retrieves an IntegrationConnection object.

Retrieve an IntegrationConnection

Returns a list of all IntegrationConnections belonging to your EndUsers.

List all IntegrationConnections

An AuthSession is the secure way to programmatically launch the client-side Conductor authentication flow that lets your users connect their accounts to your integration.

The AuthSession object

Create an AuthSession

Retrieve an AuthSession

An FAQ guide written for the end-users of Conductor's QuickBooks Desktop integration.

QuickBooks Desktop FAQ for end-users

How to fix: "Your QuickBooks Desktop connection is not active"

How to fix: "Could not start QuickBooks"

How to fix: "Do you want to allow this app to make changes to your device?"

How to fix: "QBWC1039: Unique OwnerID/FileID pair value required"

How to fix: "QBWC1085: There was a problem with the log file"

How to fix: "Unable to cast COM object of type System.__ComObject..."

Set up the QuickBooks Web Connector to automatically launch and run in the background whenever you start your computer.

Ensure the QuickBooks Web Connector opens at startup

Conductor will not function properly if multiple versions of QuickBooks Desktop are installed on the same computer.

Ensure only one version of QuickBooks Desktop is installed

Learn how to remove Conductor's QuickBooks Desktop integration from the QuickBooks Web Connector on your computer.

Overview

Usage

QuickBooks Desktop

QuickBooks Desktop API Examples

Core Resources Reference

Terminology

Term	Definition
EndUser	A user of your application for whom you will connect integrations through Conductor. Each EndUser can represent an individual or an entire company/organization of multiple users within your application.
Integration	A third-party service you want to connect to your application. For example, QuickBooks Desktop.
IntegrationConnection	A connection for a specific EndUser to a specific integration. For example, a connection for the company “ABC Company” to their QuickBooks Desktop instance.