Overview

This guide provides step-by-step instructions for registering an application on the Intuit Developer Portal and obtaining the API credentials (Client ID and Client Secret) required to integrate with QuickBooks Online. Following these steps will allow your application to authenticate with Intuit's OAuth 2.0 framework and interact securely with QuickBooks accounting and payment data.

The registration process consists of three major phases:

• Creating a Workspace (organizational container for your apps)
• Creating and Configuring an App within the Workspace
• Completing the Compliance Questionnaire to unlock Production credentials

Prerequisites

Before proceeding, ensure that the following requirements are in place:

• An active Intuit account with valid login credentials
• A registered company or business entity (used during workspace setup)
• Your application's technical details ready, including:
  • Host domain URL - qboconnect.qodbc.com
  • Launch URL - https://www.qodbc.com/links/qodbconlineconnectinfo.htm
  • Disconnect URL - https://www.qodbc.com/links/qodbconlinereconnectinfo.htm
  • Redirect URI(s) - https://qboconnect.qodbc.com/clientkey/callback.php
  • Privacy policy URL - https://qodbc.com/privacy-policy/
• Access to the Intuit Developer Portal at https://developer.intuit.com

Part 1: Sign In to the Intuit Developer Portal

Open a web browser and navigate to https://accounts.intuit.com/. Enter your credentials and click Sign In.

Navigate to https://developer.intuit.com/workspaces. This is the central hub where you manage all your developer workspaces and applications.

Part 2: Create a New Workspace

A Workspace is an organizational container that groups applications together and stores business information for compliance.

Click the + (plus) button. This opens the Create a workspace landing page. Click Get Started.

Provide a descriptive name (e.g., "Acme Corp Integration Workspace") and click Next.

Enter your legal company name and address. Ensure this matches official records for the compliance review.

Fill in the contact name, email, and phone number for developer alerts.

Click Open Workspace to enter the dashboard.

Part 3: Create a New Application

Click the + (plus) button inside the workspace and click Get Started.

Enter your product name (e.g., "Acme Accounting Sync"). Avoid using "QuickBooks" or "Intuit" in the name.

Select com.intuit.quickbooks.accounting or payment as needed. Click Done.

Review the summary and click Confirm.

Part 4: Retrieve Development API Credentials

Click Open App to access settings and credentials.

Select Keys and credentials from the left sidebar.

Toggle Show credentials under Development to copy your Client ID and Client Secret.

Part 5: Complete App Details for Production Access

To unlock Production credentials, complete the Settings sections: Basic Info, App URLs, Terms of Service, Categories, Geolocation, and Accepted Connections.

Part 6: Complete the Compliance Questionnaire

Submit the Compliance assessment to evaluate security and data handling.

Click Compliance in the sidebar and select Start questionnaire.

Shortcutting the Questionnaire

If applicable, selecting the 5th checkbox in the first question of App Information may allow you to skip certain sections by answering only two key questions regarding instructions and Re-CAPTCHA.

Part 7: Verify Redirect URIs and Retrieve Production Credentials

Ensure your Production Redirect URIs use HTTPS and point to your live server.

Once approved, return to Keys and credentials to find the unlocked Production section.

Part 8: Configure Your Application (QODBC Example)

Navigate to: Start > QODBC Driver for QuickBooks Online > Configure 64-Bit > System DSN > QuickBooks Online Data > Configure.

Troubleshooting

• Production Locked: Ensure all App Details sections are saved and the questionnaire is submitted (not just drafted).
• OAuth Errors: Double-check for Redirect URI mismatches (including trailing slashes).
• Invalid Credentials: Verify you aren't using Development keys in a Production environment.

Problem Description:

I have installed QODBC Online build 358.

I can connect to the QuickBooks Online company file using QODBC Online 32-bit DSN.

I have created a new QODBC Online DSN 64-Bit.

When I am trying to connect to the QuickBooks Online company file using QODBC Online 64-Bit DSN, on the browser, it says connected, but the DSN still shows "Connect to QuickBooks," and it does not connect.

Sometimes the DSN window disappears.

Solution:

Updates (2025-05-30):

We are currently working on fixing the issue, and we will soon release a new build.

The issue is limited to when using the new QODBC Online 64-bit DSN.

If you are using a single QuickBooks Online company file, you can use "QuickBooks Data Online" from a 32-bit system.

Once you connect to your QuickBooks Online company file using a 32-bit "QuickBooks Online Data" DSN, this will automatically update your "QuickBooks Online Data" 64-bit.

You should be able to use "QuickBooks Online Data" 64-bit.

If you wish to create your own QODBC Online DNS, you can use one of the following workarounds.

Workaround 1:

Use QODBC Online 32-bit DSN, connect to the QuickBooks Online company file.

Once connected, export the connection key from the 32-bit.

LICENSE:

LICENSER grants to you a limited, non-exclusive license to (i) install and operate the copy of the computer program contained in this package ("Program") on a single computer (one central processing unit) utilizing a single operating system and (ii) make archival copies of the program for backup purposes only for use with the same computer.

The serial number issued to you for this product indicates the QuickBooks Desktop edition year versions the QODBC Driver is licensed to use with. The serial number/registration code containing the year "24" at positions 2 and 3 is registered to work with QuickBooks 2003 or above versions as long as your QODBC Desktop subscription remains in active status. If the registration code is set to "23", it will work with QuickBooks 2023 and lower versions, and so on. If the subscription status is nonactive or has been terminated for any reason, QODBC will cease to continue working with QuickBooks 2024 or higher editions. If you have no serial number, you are using a 30-day evaluation version.

You agree to affix a label to the archival copies that contains the copyright notice printed on the original disk or tape from which the copy is made. LICENSER retains all rights to the program not expressly granted in this agreement.
OWNERSHIP OF PROGRAMS AND COPIES: This license is not a sale of the original program or any copies thereof. LICENSER retains ownership of the program and all documents, regardless of the form in which the copies may exist. The Program and accompanying manual(s) ("Documentation") are copyrighted works of authorship and may contain valuable trade secrets and confidential information proprietary to LICENSER. The Program and the Documentation may not be copied, modified, or transferred without the express written permission of the LICENSER. You agree to exercise reasonable efforts to protect LICENSER'S proprietary interest in the Program and Documentation and maintain them in strict confidence.

USER RESTRICTIONS: You may physically transfer the program from one computer to another, provided it is operated only on one computer. You may not electronically transfer such a Program. You may not translate, modify, adapt, disassemble, decompile, or reverse engineer the program. Versions of this product not designated as "Web Version" may not be used in a web service, time-sharing, or service bureau operation. You may not create derivative works based on such Program, Documentation, or any portions thereof.

TRANSFER: The Program is provided for use in your internal commercial business operations and must remain upon premises owned or leased by you. You may not rent, lease, sublicense, sell, assign, pledge, transfer, or otherwise dispose of the Program or the Documentation, on a temporary or permanent basis, without the prior written consent of LICENSER.

TERMINATION: This license is effective until terminated. This license will terminate automatically without notice from the LICENSER if you fail to comply with any provision of this license. Upon termination, you must cease all use of the program and return it, any copies thereof, including any archival copies, and the Documentation to LICENSER.

GENERAL: This license shall be governed and construed in accordance with the laws of the State of Nevada. It shall in no way affect the validity or enforceability of the Agreement. If a provision of this agreement shall be held unenforceable, it shall be deemed severable from the remaining provisions. The headings and captions used in this agreement are for convenience only and are not to be considered in construing or interpreting this agreement.

QODBC Limited Warranties and Limitation Of Liability

LIMITED WARRANTY: LICENSER grants you as the original user of the program a limited warranty that (i) the media on which the program is distributed and the Documentation will be free of material defects for a period of NINETY (90) DAYS, and (ii) the program will perform substantially by the material descriptions in the Documentation for a period of NINETY (90) DAYS. These limited warranties commence on the day you obtain the program and extend only to you, the original customer. These limited warranties give you specific legal rights, and you may have other rights which vary from state to state. Statements or representations which add to, extend, or modify these warranties are unauthorized by LICENSER and should not be relied upon by you.

DISCLAIMER: EXCEPT AS SPECIFIED ABOVE, THE LICENSER MAKES NO WARRANTIES OR REPRESENTATIONS, EXPRESS OR IMPLIED, ORAL OR WRITTEN, REGARDING THE PROGRAM, MEDIA, OR DOCUMENTATION AND HEREBY EXPRESSLY DISCLAIMS ALL OTHER EXPRESS AND IMPLIED WARRANTIES, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. LICENSER DOES NOT WARRANT THE PROGRAM WILL MEET YOUR REQUIREMENTS, OR THAT ITS OPERATION WILL BE UNINTERRUPTED OR ERROR-FREE.

EXCLUSIVE REMEDY: Your sole and exclusive remedy in the event of a breach of the limited warranty set forth above is limited to either repair or replacement of the program or the Documentation by LICENSER or refund of your money, at Licenser's sole discretion. To obtain warranty service, however, you must return the nonconforming item, with proof of the date you obtained it, to LICENSER no later than TEN (10) days after the expiration of the applicable limited warranty period. If LICENSER determines that the particular item has been damaged by accident, abuse, misuse, or misapplication, or has been modified without the written permission of LICENSER, or if any

The LICENSER label or serial number has been removed or defaced, the limited warranties above do not apply, and you accept full responsibility for the product.

LIMITATION OF LIABILITY: LICENSER AND ALL PARTIES INVOLVED IN THE CREATION OR DELIVERY OF THE PROGRAM OR DOCUMENTATION TO YOU SHALL HAVE NO LIABILITY TO YOU OR ANY THIRD PARTY FOR SPECIAL, INCIDENTAL, INDIRECT, EXEMPLARY, AND CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOSS OF PROFITS, GOODWILL OR SAVINGS, DOWNTIME, DAMAGE TO OR REPLACEMENT OF EQUIPMENT AND PROPERTY OR RECOVERY OR REPLACEMENT OF PROGRAMS OR DATA) ARISING FROM CLAIMS BASED IN WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT TORT OR OTHERWISE, EVEN IF LICENSER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH CLAIM OF DAMAGE. THE LICENSE'S LIABILITY FOR DIRECT DAMAGES SHALL NOT EXCEED THE ACTUAL AMOUNT PAID FOR THE PRODUCT.

Issue:

We created a new QODBC 32-Bit DSN with the name "QODBC-MyCompany.

The DSN was created successfully.

We tried to change the "Mode when opening" to "Single-user Mode" or "Multi-user Mode," applied the changes, and closed the QODBC Setup Screen.

The changes are not saved.

We tried changing the company file path, but the same issue.

Reason:

We have identified the issue and are currently working on the fix.

The issue is limited to the QODBC Desktop build 348.

Solution:

Please download and install the QODBC build 349 or above. - https://qodbc.com/download/desktop

Workaround:

Create a new QODBC 64-Bit DSN with the same name as your QODBC 32-Bit DSN.

After creating a 64-Bit DSN of the same name, you can apply the changes to your 32-Bit DSN.

Please raise a support ticket with us if you do not wish to apply the above workaround. We will help you with downgrading QODBC to build 345 or 346.

Click here to raise a support ticket.

Problem Description:

Unable to use QODBC Online on Windows 7

Error - session failed. 653 - There was an error while communicating with the Ids Server. - - The Response Stream was null or empty

Solutions: 

You must enable TLS 1.1 and TLS 1.2 on the Windows 7 OS.

To allow QODBC Online to communicate securely with the Intuit QuickBooks Online server using TLS 1.1 and TLS 1.2, you have to do the following:

Please enable the internet connection on your machine. Please follow the steps below to enable TLS 1.2 on your system.

Follow the steps below to launch 'Services' from the start menu:

Click the Windows Start button from the desktop and search for the keyword 'Services.'

Click on 'Services' to launch the 'Services' application.

Start the two services below:

1) Background Intelligent Transfer System (Right-click and go to "Properties" and select start type as "Automatic" and click on the "Start" button)

2) Windows Update (Right-click and go to "Properties" and select start type as "Automatic" and click on the "Start" button)

Create a folder named TLS12 in your C: drive.

Download the two files below and place them in the TLS12 folder.

install-kb.ps1

tls-reg-edit.ps1

To download the compressed file - click here

Run PowerShell (without x86) from the Start menu as "Run as administrator."

In the PowerShell command prompt, navigate to the TLS12 folder and execute the commands below one by one.

PS C:\Windows\system32> cd\

PS C:\> cd .\TLS12

PS C:\TLS12> Set-ExecutionPolicy Bypass -Scope Process ; .\install-kb.ps1

Type "Yes" and press the "Enter" key.

It will update the system to KB3140245.

Restart your machine.

Run PowerShell (without x86) from the Start menu as "Run as administrator."

In the PowerShell command prompt, navigate to the TLS12 folder and execute the commands below one by one.

PS C:\Windows\system32> cd\

PS C:\> cd .\TLS12

PS C:\TLS12> Set-ExecutionPolicy Bypass -Scope Process ; .\tls-reg-edit.ps1

Type "Yes" and press the "Enter" key.

Restart your machine.

After restarting the machine, launch the QODBC Online Test Tool from Start Menu>> QODBC Driver for use with QuickBooks Online>> QODBC Online Test Tool.

Connect using the DSN' QuickBooks Online Data'.

You should be able to connect.

Source of PS  -  How+to+Configure+Microsoft+Windows+7+to+use+TLS+Version+1.2

If you are still facing the issue, install the Windows update KB3140245, either through Windows Update, where it is available as an Optional Update, or download it from the Microsoft Update Catalog (www.catalog.update.microsoft.com).

Download the file MicrosoftEasyFix51044.msi from the following page and install it on your computer:

Update-to-enable-tls-1-1-and-tls-1-2-as-a-default-secure-protocols-in

The file is available for download in the section labeled Easy To Fix on the above-mentioned page. Suppose the easy fix option is not suitable for you, and you prefer to manually edit your computer's registry. In that case, the article also provides that information in the section "How the DefaultSecureProtocols registry entry works."

If you are still facing the issue, please raise a support ticket to the QODBC Technical Support Department from the link below & provide the requested information:

Submit a Ticket

Please attach the following files:

1) Screenshot of QODBC Setup Screen -- > About

2) Screenshot of the issue you're facing.

Share the entire log files as an attachment in text format from

3) QODBC Setup Screen -- > Messages -- > Review QODBC Messages

4) QODBC Setup Screen -- > Messages -- > Review SDK Messages

Refer to: How to take a screenshot: How to take a screenshot

Tags: QuickBooks Online, QBO, OAuth, Windows 7, TLS, Unable to connect, QODBC Online, QO

Problem Description:

So the QODBC works excellently running on the machine. We intend to integrate into our website / Intranet to create customers or make changes from the web. I noticed QuickBooks needs to be logged in and open to function. Is there a server version that will not require a user to log in or pass the info along automatically, so the website continues to function correctly?

Is there a way to try the server version by syncing to the SQL server? I need to be able to dump the customer table once daily into SQL. Maybe other tables in the future, like orders or quotes. Does the server version need a remote desktop session open to work? If the server reboots because of an update, I need to log in to make it work again. That doesn’t seem very feasible for us. 

Solution:

QODBC is not a driver you would install on a server; multiple workstations would have access to it. The server version of QODBC is for synchronizing SQL Server with QuickBooks data or for a web or intranet application.

>>Is there a server version that will not need a user logged in or pass the info along automatically, so the website continues to function correctly?
>>Does the server version need to have a remote desktop session open to work?

Please refer to how to Setup QODBC to Access QuickBooks when no one Logged in.

OR

You may configure a session-0 to start and start QuickBooks and QRemoteServer automatically.
When you configure session-0, you are setting up the auto login of a user, and that user will have a desktop session running.

>>Is there a way to try the server version by syncing to the SQL server?

You can use La inked Server on SQL Server and connect to QuickBooks Data using QRemote. When you query the Linked Server/tables, you will always get live QuickBooks Data.

For a dump of all the tables or selected tables from QODBC to Tables in SQL Server Database, you may write a script to create the table(s) in SQL Server and get data from the linked server.

e.g.
SELECT * into LocalSQLTableName FROM OPENQUERY(YourLinkedServerName, 'SELECT * FROM LinkedTableName')

SELECT * into tblVendor FROM OPENQUERY(QRemote, 'SELECT * FROM Vendor')

You can add the script to the agent to run periodically.

Please refer to the below-mentioned article for How to create a Link Server with MS SQL 2005/2008/2012 Using QODBC/QRemote.

For 32-bit SQL Server, refer to:
How to create a Link Server with MS SQL 2005/2008/2012 32-bit Using QODBC/QRemote

For 64-bit SQL Server, refer to:
How to create a Link Server with MS SQL 2005/2008/2012 64-bit Using QODBC/QRemote


Also, Refer:
How to set up QODBC Driver to auto-connect to QuickBooks. (Video)
How to setup QODBC for Auto-login into QuickBooks