We’re pleased to unveil our new webhooks page on the Intuit Developer portal. The revamped page comes with some powerful new features designed to optimize your workflows and improve your integration.
Fresh look and feel
We’ve updated the webhooks page to reflect the modern design of our new developer portal. The refreshed design offers enhanced clarity, making it easier to explore and understand the events available for subscription. We’ve also made your security more important by adding controls that let you change the visibility of your verifier token value. This will make sure your sensitive information stays safe.
New functionality
We’ve introduced two new features accessible from the Actions dropdown menu: ‘Delete subscription’ and ‘Send test events’.
The ‘Delete subscription’ option enables you to effortlessly remove all webhook subscriptions associated with your app and reset the endpoint URL field, ensuring you no longer receive webhook notifications for your connected QuickBooks companies.
The ‘Send test events’ option enables you to receive sample webhook notifications directly to your configured endpoint. This allows you to preview the event format without needing to log into a QuickBooks Online account or trigger an actual event. When your app is set up to receive webhook notifications, you can use them to validate that your app handles the requests correctly. Select ‘Send’ and we’ll dispatch a POST request to your endpoint URL with the chosen event type.
More reliable delivery mechanism
In addition to improving the portal, we’ve recently revamped our webhooks architecture to create a more reliable platform.
When an event occurs in QuickBooks Online that your app is subscribed to, it’s added to a delivery queue to be sent to the endpoint configured as your webhooks listener. Instead of sending events as separate notifications, we put them all together and send them in the order they happened. This makes it easier to understand which events were sent to your endpoint and which events didn’t get delivered.
If your app fails to respond to a webhook event with an HTTP 200 status code within three seconds, or it returns a 500 (or other) error status, we’ll assume your endpoint is having issues and attempt to resend the event. When we start to resend the events, there will be a few seconds between attempts which gradually increase to making attempts every six hours. We won’t proceed with the queue until we receive an HTTP 200 status code, which ensures that all events have been successfully delivered to you.
Next steps
This new experience is automatically available to you when you sign in to your developer account at https://developer.intuit.com. To effectively use the webhooks platform, ensure your app responds to a webhooks notification with an HTTP 200 status code within three seconds. As prescribed in our best practices for using webhooks, avoid processing the notification payload or executing complex operations on the same thread that you receive the notification. Your app should queue the events that Intuit sends and process them asynchronously on your side.
Share your feedback with us so we can continue to improve your experience.