[QODBC-Online] - How to Register an App on the Intuit Developer Portal and Generate API Keys

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.