Webhooks are notifications about QuickBooks entities that are sent to developer-created applications.

If you wish to be notified when a customer’s information changes, you may configure a specific endpoint that QuickBooks can call for this event with the details of the change.

When webhooks is active, data for the requested event is aggregated and then sent in a periodic notification to your call back URL or service. Once you have configured webhooks, you will receive event notifications for all companies your app is connected to. Note: Only when you have a valid OAuth connection with a company, your webhooks endpoint will receive the webhooks for that company.

Configuring webhooks

You can enable webhooks on a per-app basis via the Webhooks section under Development or Production. See a full list of entities and operations supported here.

There are two webhooks sections: webhooks for development and webhooks for production. The former is for testing on your development setup, while the latter is for use with your app once it has been released to production. Make sure to configure both appropriately. For both development and production , webhooks will fire near real time. However for production, developers can configure for how long Intuit should aggregate events for their application to 0 Minute (real-time), 1 Minute, 3 Minutes, or 5 Minutes. Default being the 0 Minute(real-time). However, this aggregation may be delayed during peak times.

  1. From your My Apps dashboard, click the app you wish to configure.

  2. Click the Webhooks section under Development or Production.

  3. Enter your endpoint URL in the field provided. This URL must be exposed over the internet and be secured via HTTPS. Note: Make sure that your specified domain has intermediate certificates installed to complete the chain of trust. Self-signed certificates are not supported.

  4. Click show webhooks to view webhook events.

  5. Check the events desired (or ENTITY to enable all of them).

  6. Click Save. It may take up to five minutes for your endpoint to receive its first notification.



When you are testing webhooks with your app, you must configure webhooks in the sandbox environment. Your app must have gone through OAuth flow and authorization with a sandbox company before events will be received. Once you are ready to go to production, you must configure webhooks again on the production side.

Best practices

Refer here for information on how to process webhooks notifications.

Sample apps

Refer to the following links for sample webhooks implementations.