Intuit QuickBooks

Intuit QuickBooks is a comprehensive accounting and financial management platform designed for small and medium-sized businesses, providing tools for invoicing, expense tracking, payroll management, tax preparation, and financial reporting to streamline business operations and ensure financial compliance.

Power end-to-end data operations for your Intuit QuickBooks API with Nexla. Our bi-directional Intuit QuickBooks connector is purpose-built for Intuit QuickBooks, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Intuit QuickBooks or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Intuit QuickBooks workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Intuit QuickBooks credential, you need to have a QuickBooks account. The credential uses the Nexla App for OAuth2 authentication, which simplifies the setup process by using a pre-configured OAuth2 application managed by Nexla.

To use this credential, you need to have a QuickBooks account. Once you have access to your account, you can connect it to Nexla using the OAuth2 authorization flow. The Nexla App handles the OAuth2 authentication process, so you do not need to create your own OAuth2 application. For detailed information about QuickBooks API authentication and setup, refer to the QuickBooks API documentation.

Authenticate

Credentials required

Nexla client for connecting to QuickBooks account

Field	Required	Secret	Description
API Access Scope	Yes	No	API Access Scope Allowed values: Accounting API; Payments API; Accounting & Payments API

Create a credential in Nexla

1. To create a new Intuit QuickBooks credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Intuit QuickBooks

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Select the API access scope from the API Access Scope dropdown menu. Available options include:

   • Accounting API: com.intuit.quickbooks.accounting openid email profile
   • Payments API: com.intuit.quickbooks.payment openid email profile
   • Accounting & Payments API: com.intuit.quickbooks.accounting com.intuit.quickbooks.payment openid email profile

   The default value is com.intuit.quickbooks.accounting openid email profile if not specified. The selected scope determines what permissions are requested during the OAuth2 authorization flow.

4. Click the Authorize button to begin the OAuth2 authorization flow. This will redirect you to Intuit's authorization page where you will be asked to sign in with your QuickBooks account and grant permissions to Nexla to access your QuickBooks data.

   During the OAuth2 authorization flow, you will be redirected to Intuit's authorization page. You must sign in with a QuickBooks account that has access to the QuickBooks company you want to connect. After signing in, you will be asked to grant permissions to Nexla to access your QuickBooks data. The access scopes determine what permissions are requested. Once you grant permissions, you will be redirected back to Nexla, and the authorization will be completed automatically.

5. After completing the OAuth2 authorization flow, Nexla will automatically obtain and store the access token and refresh token needed to authenticate API requests. The access token is used to authenticate each API request, and the refresh token is used to obtain new access tokens when the current access token expires.

   OAuth2 access tokens expire after a certain period for security reasons. Nexla automatically refreshes expired access tokens using the refresh token, so you typically do not need to re-authorize unless you revoke access or the refresh token expires. The access token is sent in the Authorization header with the Bearer prefix for all API requests to the QuickBooks API. For detailed information about OAuth2 authentication, token management, and available scopes, see the QuickBooks API documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Intuit QuickBooks connector tile, then select the credential that will be used to connect to the QuickBooks account, and click Next; or, create a new Intuit QuickBooks credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common QuickBooks endpoints. Each template is designed specifically for the corresponding QuickBooks endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Get Records of Type

Returns all records of a specific resource. Use advanced tab for customizing slices of data to be fetched.

• Enter the QuickBooks Online Company ID (Realm ID) in the QuickBooks Online Company ID/ Realm ID field. This is the unique identifier of your QuickBooks company. You can get it from your Settings >> Account and settings >> Billing & Subscription page, or by clicking Control + Option + ? in your account.
• Select or enter the type of resource whose records you wish to fetch in the Resource Type field. Available options include Customer, Account, Invoice, CompanyInfo, Bill, Employee, and Vendor. You can also add custom resource types if needed. The default value is Customer if not specified.
• Enter the API minor version in the API Minor Version field. This determines which minor version of the QuickBooks API you wish to access. The default value is 65 if not specified.
• The endpoint uses GET requests to https://quickbooks.api.intuit.com/v3/company/{realm_id}/query?query=Select+*+from+{resource_type}+maxresults+1000&minorversion={minorversion} where {realm_id} is the QuickBooks Online Company ID you provide, {resource_type} is the Resource Type you select, and {minorversion} is the API Minor Version you provide. The endpoint URL is automatically constructed based on the QuickBooks API base URL and all the parameters.
• The endpoint does not use pagination (iteration.type: static.url) and returns a single response. The response data path is $.QueryResponse.{resource_type}[*], which extracts all items from the resource type array in the API response.

This endpoint retrieves all records of a specific resource type from your QuickBooks account. The endpoint uses a simple SELECT query to fetch all records of the specified resource type, with a maximum of 1000 results per request. You can customize the data to be fetched using the advanced tab. The endpoint supports various resource types including customers, accounts, invoices, company information, bills, employees, and vendors. For detailed information about available resource types and the API response format, see the QuickBooks API documentation.

Perform Custom Query to Fetch Records

Perform a query to fetch records from the QuickBooks API.

• Enter the QuickBooks Online Company ID (Realm ID) in the QuickBooks Online Company ID/ Realm ID field. This is the unique identifier of your QuickBooks company. You can get it from your Settings >> Account and settings >> Billing & Subscription page, or by clicking Control + Option + ? in your account.
• Enter the query statement to be executed in the Query field. Note that the query can only be run on the resource type. The default value is Select * if not specified. You can specify which fields to select in your query.
• Select or enter the type of resource whose records you wish to fetch in the Resource Type field. Available options include Customer, Account, Invoice, CompanyInfo, Bill, Employee, and Vendor. You can also add custom resource types if needed. The default value is Customer if not specified.
• Enter the query filter in the Query Filters field. This is usually a combination of WHERE clauses and maxresults to be fetched. The default value is startposition 0 maxresults 1000 if not specified. You can use WHERE clauses to filter records based on specific conditions.
• Enter the API minor version in the API Minor Version field. This determines which minor version of the QuickBooks API you wish to access. The default value is 65 if not specified.
• The endpoint uses GET requests to https://quickbooks.api.intuit.com/v3/company/{realm_id}/query?query={query}+from+{resource_type}+{query_condition}&minorversion={minorversion} where {realm_id} is the QuickBooks Online Company ID you provide, {query} is the Query you provide, {resource_type} is the Resource Type you select, {query_condition} is the Query Filters you provide, and {minorversion} is the API Minor Version you provide. The endpoint URL is automatically constructed based on the QuickBooks API base URL and all the parameters.
• The endpoint does not use pagination (iteration.type: static.url) and returns a single response. The response data path is $.QueryResponse.{resource_type}[*], which extracts all items from the resource type array in the API response.

This endpoint allows you to perform custom queries to fetch records from your QuickBooks account. The endpoint supports custom SELECT queries with WHERE clauses and filtering options, giving you full control over which records are retrieved. You can specify which fields to select, filter records based on specific conditions, and control pagination using startposition and maxresults. The endpoint supports various resource types including customers, accounts, invoices, company information, bills, employees, and vendors. For detailed information about query syntax, available resource types, and the API response format, see the QuickBooks API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Intuit QuickBooks data sources can also be manually configured to ingest data from any valid QuickBooks API endpoint, including endpoints not covered by the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the content format, API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

QuickBooks API endpoints typically follow the pattern https://quickbooks.api.intuit.com/v3/company/{realm_id}/{endpoint_path}, and the QuickBooks API typically returns data in JSON format. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration, and the endpoint URL must include your QuickBooks Online Company ID (Realm ID) in the path. For detailed information about QuickBooks API endpoints and available APIs, see the QuickBooks API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Intuit QuickBooks data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Intuit QuickBooks destination, and select the Send to Destination option from the menu. Select the Intuit QuickBooks connector from the list of available destination connectors, then select the credential that will be used to connect to the QuickBooks organization, and click Next; or, create a new Intuit QuickBooks credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common QuickBooks endpoints. Each template is designed specifically for the corresponding QuickBooks endpoint, making destination setup easy and efficient. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Records of a Resource

Use this endpoint to create records of a specific resource using records from a Nexset. Please see the QuickBooks API document for required record structure.

• Enter the QuickBooks Online Company ID (Realm ID) in the QuickBooks Online Company ID/ Realm ID field. This is the unique identifier of your QuickBooks company. You can get it from your Settings >> Account and settings >> Billing & Subscription page, or by clicking Control + Option + ? in your account.
• Enter the type of resource whose records you wish to create in the Resource Type field. This should match the resource type you want to create (e.g., Customer, Account, Invoice, etc.).
• The endpoint uses POST requests to https://quickbooks.api.intuit.com/v3/company/{realm_id}/{resource_type} where {realm_id} is the QuickBooks Online Company ID you provide and {resource_type} is the Resource Type you provide. The endpoint URL is automatically constructed based on the QuickBooks API base URL and all the path parameters.
• The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the resource data to create.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a resource record. If you need to create multiple records, you can send multiple records, but each will be processed as a separate request.
• This endpoint does not automatically create a data source to track the responses received from the QuickBooks API after each call.

The request body must be properly formatted JSON that matches the QuickBooks API specification for creating resources. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Please check the QuickBooks API documentation for the required record structure for the resource type you want to create. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating resources, including required fields, field names, and request formats, see the QuickBooks API documentation.

Full Update Records of a Resource

Use this endpoint to update an existing resource. Nexset records must include all writable fields of the existing resource as returned in a read response. Fields not present are set to NULL.

• Enter the QuickBooks Online Company ID (Realm ID) in the QuickBooks Online Company ID/ Realm ID field. This is the unique identifier of your QuickBooks company. You can get it from your Settings >> Account and settings >> Billing & Subscription page, or by clicking Control + Option + ? in your account.
• Enter the type of resource whose records you wish to update in the Resource Type field. This should match the resource type you want to update (e.g., Customer, Account, Invoice, etc.).
• The endpoint uses POST requests to https://quickbooks.api.intuit.com/v3/company/{realm_id}/{resource_type} where {realm_id} is the QuickBooks Online Company ID you provide and {resource_type} is the Resource Type you provide. The endpoint URL is automatically constructed based on the QuickBooks API base URL and all the path parameters.
• The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the resource data to update.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to update a resource record. If you need to update multiple records, you can send multiple records, but each will be processed as a separate request.
• This endpoint does not automatically create a data source to track the responses received from the QuickBooks API after each call.

The request body must be properly formatted JSON that matches the QuickBooks API specification for updating resources. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Important: This is a full update operation, which means Nexset records must include all writable fields of the existing resource as returned in a read response. Fields not present in the update request are set to NULL. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about updating resources, including required fields, field names, and request formats, see the QuickBooks API documentation.

Manual configuration

Intuit QuickBooks destinations can also be manually configured to send data to any valid QuickBooks API endpoint, including endpoints not covered by the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the content format, API method, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

QuickBooks API endpoints typically follow the pattern https://quickbooks.api.intuit.com/v3/company/{realm_id}/{endpoint_path}, and the QuickBooks API typically uses JSON format for request bodies. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration, and the endpoint URL must include your QuickBooks Online Company ID (Realm ID) in the path. For detailed information about QuickBooks API endpoints and available APIs, see the QuickBooks API documentation.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Intuit QuickBooks endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Intuit QuickBooks endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.