Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "QuickBooks" |
| 4 | description: "Public support knowledge for QuickBooks." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-16T00:00:00Z" |
| 8 | tags: |
| 9 | - "quickbooks" |
| 10 | --- |
| 11 | # QuickBooks |
| 12 | |
| 13 | |
| 14 | ## Use the sandbox QuickBooks API base URL for sandbox connections |
| 15 | |
| 16 | For QuickBooks sandbox accounts, pass `https://sandbox-quickbooks.api.intuit.com` as the URL/base URL when initiating the connection. Production connections should use the production Intuit API base URL. |
| 17 | |
| 18 | ## QuickBooks auth configs need QuickBooks credentials and matching redirect URL |
| 19 | |
| 20 | When creating a QuickBooks auth config, enter the QuickBooks OAuth credentials from the Intuit developer app and configure the Composio redirect URL in the QuickBooks auth app. A mismatch or missing redirect URL can break the OAuth flow. |
| 21 | |
| 22 | ## QuickBooks auth can accept custom auth and token URLs for sandbox/custom flows |
| 23 | |
| 24 | QuickBooks toolkit support was updated to accept auth and token URLs during connection initiation. If a customer needs sandbox or custom Intuit OAuth endpoints, use a toolkit version that supports passing those URLs. |
| 25 | |
| 26 | ## QuickBooks payment scope requires payment module access |
| 27 | |
| 28 | If the QuickBooks OAuth flow includes the payments scope `com.intuit.quickbooks.payment`, the QuickBooks payment module must be enabled for that account/app. If the customer does not need payment tools, remove that scope and retry the connection. |
| 29 | |
| 30 | ## Realm ID mapping fixes may require the latest QuickBooks toolkit version |
| 31 | |
| 32 | For QuickBooks realm/company mapping issues, retry on the latest toolkit version rather than a historical pinned version. |
| 33 | |
| 34 | ## Multiple QuickBooks accounts can be selected in Claude/MCP by using separate user IDs or connected account IDs |
| 35 | |
| 36 | Create separate connected accounts for each QuickBooks account, preferably with distinct `user_id` values. In Claude/MCP setup, append the desired `connected_account_id` or `user_id` to the MCP URL/configuration so the session targets the intended QuickBooks connection. |
| 37 | |
| 38 | ## QuickBooks tokens are refreshed periodically with retries before expiring the connection |
| 39 | |
| 40 | QuickBooks OAuth refresh is handled by Composio through the provider's token endpoint. The current refresh path retries transient failures and uses credential-expiry timing rather than promising a fixed 15-minute schedule. If the provider conclusively rejects the grant or failures persist past the platform's retry budget, the connected account expires and the user must reauthenticate through a new auth link. |
| 41 | |
| 42 | ## QuickBooks hosted auth screen can be skipped by sending users directly to the OAuth provider |
| 43 | |
| 44 | The Composio auth screen can be skipped for QuickBooks by sending users directly to the OAuth provider, following Composio's white-labeling/direct-provider auth flow. Use this when the customer wants the user to see the provider consent screen without the intermediate Composio auth screen. |