> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/quickbooks.md). # Quickbooks First, you need to set a Quickbooks key and endpoint through the Backoffice in order to provide the Quickbooks components to your customers. Go to the to create a new app.

Select the name and scope:

Then you receive your *clientID* and *clientSecret*. Intuit issues two separate key pairs: **Development keys** work only with sandbox companies and **Production keys** work only with production companies. Configure the pair that matches the companies your users will connect. Also add the redirect URL. Example: `https://api.YOUR_SUBDOMAIN.appmixer.cloud/auth/quickbooks/callback`.

Go the Appmixer BackOffice -> Configuration. Add new configuration: `appmixer:quickbooks` Add your *clientId* and *clientSecret* keys. When you use the **Development (sandbox) keys**, also add `sandbox`: `true` to the same configuration — it switches the connector to the sandbox API base URL (`sandbox-quickbooks.api.intuit.com`) and the sandbox OpenID endpoint. With Production keys, omit the flag (production is the default). ## Webhooks All trigger components (for example `NewInvoice`) use QuickBooks webhooks. In order to use this component(s) in Appmixer, you have to register Appmixer's QuickBooks URI in QuickBooks first and set the webhook key in the Appmixer BackOffice. Go to then choose your Appmixer app. Navigate to the "Webhooks" section either for the sandbox or production environment and add a new webhook.

Fill the field **Endpoint URL** with `https://api.acme.appmixer.cloud/plugins/appmixer/quickbooks/webhooks` (replace `acme` with your subdomain). In **Subscribed events**, select the entities and operations the trigger components consume: | Entity | Operations | Trigger components | | -------- | -------------- | ---------------------------- | | Customer | Create, Update | NewCustomer, UpdatedCustomer | | Invoice | Create, Update | NewInvoice, UpdatedInvoice | Leave the **Enable cloud event payload format** toggle **off** — the connector processes the classic webhook payload format.

For detailed steps, see [QuickBooks documentation](https://developer.intuit.com/app/developer/qbo/docs/develop/webhooks#endpoints). Make sure to copy the **Verifier Token** and paste it to the Appmixer BackOffice -> Configuration -> `appmixer:quickbooks` -> `webhookVerifierToken` field. Intuit issues a **different verifier token for the Development (sandbox) and Production** webhook sections, even when both point at the same endpoint. The connector accepts multiple tokens: set the production token in `webhookVerifierToken` and the sandbox token in `webhookVerifierTokenSandbox` (or put several tokens comma-separated into `webhookVerifierToken`). Incoming events are verified against every configured token; delivery is routed by the company (`realmId`), so sandbox and production events never mix.

Appmixer BackOffice configuration for QuickBooks Webhooks

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.appmixer.com/connector-configuration/quickbooks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.