Connector Details

Connector Versions

Create OAuth app

To create a QuickBooks OAuth app, you will need to register for a free developer account on the Intuit Developer Portal.

Once you have registered for an Intuit Developer account, you should be able to access the Developer Dashboard which should look something like below:

From here, you can create an OAuth app by selecting Create an app. Select QuickBooks Online and Payments as the platform you want to develop for, as pictured below:

You will then need to provide an app name, scope, and select the teamt o access the app. hotglue integrations generally do not deal with QuickBooks Payments, so you can just select the com.intuit.quickbooks.accounting scope as pictured below:

Once done, select Create app. This will take you to the App settings page, where you can configure two separate sets of credentials:

• Development Settings gives you credentials / settings for configuring an OAuth app to access QuickBooks Online Sandbox accounts. This is only for testing purposes.
• Production Settings gives you credentials / settngs for configuring an OAuth app to access QuickBooks Online Production accounts.

For this example, I will walk through the Development Settings, as the process is the same for both. Click on Keys & credentials

You should then see a screen similar to below, where you can a Redirect URI:

From this screen, add <https://hotglue.xyz/callback> as a valid redirect URI. If you do not do this step, hotglue will not be able to make OAuth connections on your behalf. Once done, click Save

Now you can insert the client id and client secret pair from the Keys section into your hotglue QuickBooks target settings:

That's it! Just repeat the process to enable the Quickbooks Production OAuth app.

Supported Data

Below is a list of the QuickBooks entities currently supported by the hotglue target:​

Don't see an entity you're looking for? Let us know

Sample Postman Collection

Use the below Postman collection to access sample payloads for the QuickBooks target. Note: the samples are formatted to work with the API Source.