Disclaimer: QuickBooksUsers.com is an independent service operated by E-Tech Corporation and is not affiliated with, endorsed by, or sponsored by Intuit Inc. "QuickBooks" is a registered trademark of Intuit Inc., used for identification and reference purposes only. See our Terms of Service.

QuickBooks

Connecting a Custom App to QuickBooks Online Through the API

QuickBooksUsers.com TeamUpdated 2026-08-243 min read

A custom app never opens your QuickBooks Online company directly. It works through the QuickBooks Online API, and you grant access through Intuit’s OAuth 2.0 login. You sign in, pick the company, approve the permissions, and the app receives tokens it uses for every call. Here is the whole connection, from registering the app to your first successful request.

How does authorization work?

QuickBooks Online uses OAuth 2.0. When your app needs access, it sends you to an Intuit sign-in page. You log in as a QuickBooks user who owns or manages the company, pick the company to connect, and approve the scopes.

Scopes are the permissions the app asks for, such as reading accounting data or writing payments. Once you approve, Intuit sends the app an access token and a refresh token. The access token is short-lived. The refresh token lets the app keep working after it expires, without asking you to log in again.

What do you need before you start?

Two things: an Intuit developer account, which is free to create, and a company to connect to.

From the developer dashboard you register an app and receive a client ID and a client secret. These identify your app during the OAuth handshake.

For the company, start with a sandbox. The developer dashboard lets you create one, and testing there is the safer habit: a write through the API changes real data in a live file.

Where does the authorization happen in code?

The flow has three steps, and each exists for a reason.

  1. Your app builds an authorization URL containing its client ID, the scopes it needs, and a redirect URI. You open that URL in a browser and sign in. The redirect URI is the address Intuit sends you back to once you approve.
  2. Intuit redirects to that URI with a one-time code. Because the code works exactly once, its only job is the exchange in the next step.
  3. Your app exchanges the code, plus its client secret, for the tokens. The secret is what proves the request came from your app rather than an impostor.

Store the refresh token securely; losing it means the user has to authorize again. Most languages have an OAuth library that handles the exchange for you, so you rarely write the token request by hand.

Which company does the token cover?

A token is tied to the specific QuickBooks Online company you selected during authorization. API calls include a realm ID, the numeric identifier for that company. If you serve multiple companies, each one goes through its own authorization and gets its own token and realm ID.

Does the API cover everything in QuickBooks Online?

The API exposes most accounting objects: invoices, customers, payments, bills, journal entries, and more. Some things are limited or unavailable, so check whether the feature you need is supported before committing to a build. Batch sizes and request rates are also capped, which matters for large imports.

Is building against the API the right choice?

Not always. If the goal is a one-time move of data rather than an ongoing integration, a conversion service is often simpler than a custom build. If the integration is worth having but you would rather not build and maintain it yourself, our custom QuickBooks programming and integrations service takes on that work.

What should the first test be?

Keep it minimal. Authorize your app against a sandbox company, read one invoice, and print the raw response. That single round trip proves the whole chain works: registration, the redirect, the token exchange, and the realm ID. Once it succeeds, the rest is ordinary development against a documented REST interface.

Need Professional Help?

Contact Us