Logo
Home

Upcoming change to webhooks payload structure

Intuit has updated its webhooks infrastructure to the CloudEvents format, a change that brings improved standardization and flexibility. The CloudEvents protocol offers several significant improvements over the previous format. It ensures reliable data synchronization between Intuit and third-party applications and provides enhanced traceability for individual events. This update requires developers to modify their applications to handle the new format. The migration is mandatory and must be completed by May 15, 2026.

What is happening?

Intuit’s webhooks infrastructure has been updated to the CloudEvents format. Due to this, all app developers on the platform will need to start consuming webhooks notifications in the new (CloudEvents) format. The migration of notifications from the old format to the new format will require developers to make code changes so that they can continue to consume webhooks events sent by Intuit.

Here is a sample notification payload in the current format:

{
    "eventNotifications": [
        {
            "realmId": "310687",
            "dataChangeEvent": {
                "entities": [
                    {
                        "id": "1234",
                        "operation": "Create",
                        "name": "Account",
                        "lastUpdated": "2025-09-08T20:52:31.657Z"
                    }
                ]
            }
        }
    ]
}

Here is a sample notification payload in the new CloudEvents format:

[
  {
    "specversion": "1.0",
    "id": "88cd52aa-33b6-4351-9aa4-47572edbd068",
    "source": "intuit.dsnBgbseACLLRZNxo2dfc4evmEJdxde58xeeYcZliOU=",
    "type": "qbo.account.created.v1",
    "datacontenttype": "application/json",
    "time": "2025-09-10T21:31:25.179851517Z",
    "intuitentityid": "1234",
    "intuitaccountid": "310687",
    "data": {}
  }
]

What do I need to do?

We have launched a switch on the webhooks subscription page, that will allow you to enable and test the new format for your app in Sandbox and Production. We recommend that you make the switch in Sandbox, test the new format, and make the necessary changes on your end to consume the new format. If needed, you can always switch back to the old format. When you’re ready with your changes, you can do the same exercise in Production. 

Our SDKs have been updated to support both the new and the old formats. You will need to update your usage of the SDK to properly process the new event format.

  • If you are using our Java SDK, then update it to the latest version 6.5.2.
  • If you are using our PHP SDK, then update it to the latest version 6.2.2.
  • If you are using our .Net SDK, then update it to the latest version 14.7.3.
  • If you aren’t using any of our SDKs, ensure your code is able to correctly process the new event format.

Here’s a list of the fields in the new payload:

specversionValue is always 1. Can be ignored. 
idID of the event. May be useful in troubleshooting or reporting any errors.
sourceGUID value. Can be ignored. 
typeRepresents the entity and event for the notification. It’s in the format – namespace.entitytype.eventname.version
datacontenttypeapplication/json
timeTime of the notification
intuitentityidThe ID of the entity that was changed
intuitaccountidThe QuickBooks Online company ID or realm ID
dataCan be name-value pairs to represent additional data. Can be ignored if empty.

Note that in the new structure, one notification can contain a list of events, each for a different QuickBooks Online company. Your app must be updated to handle events for multiple companies per notification.

When do I need to take action?

You can take action any time from now and must complete the migration by May 15, 2026

How do I test my changes?

We will launch a switch on the webhooks subscription page, that will allow you to enable and test the new format for your app in sandbox and production. 

We recommend that you make the switch in sandbox, make the necessary changes on your end and then switch in production when you are ready. If needed, you can always switch back to the old format.

What happens if I don’t take any action? 

If you do not make a change, your app will no longer be able to process webhooks notifications from Intuit. Depending on the app workflows, your customers may see delays in their QuickBooks Online changes reflecting in your app. 

What if I have additional questions?

Connect with our developer support team by submitting a ticket, asking a question on our forums or attending our office hours. We’ll be hosting a webinar about the webhooks migration on December 4, 2025. Sign up here to attend this session and have your questions answered.


by