Fusebill supports the use of webhooks to facilitate communication with other web apps. Webhooks can be configured to automatically notify third party web apps of important events on the Fusebill side. "Event" refers to the creation or alteration of data in Fusebill such as customer, payment, or subscription data.
How Do Webhooks Differ From Polling?
In polling, an app sends a request for new events to an endpoint at a predetermined frequency. If the endpoint doesn’t respond, no new events have occurred since the last request. A webhook, by contrast, runs when a specific event occurs triggering a notification to be sent to the configured endpoint(s). Polling can be compared to a parent asking a child every 10 minutes whether they are hungry, whereas webhooks can be compared to the child signalling to the parent that they need something to eat. The event notification is sent automatically, in real-time, rather than in response to a periodic request for new events.
How Do Webhooks Work?
To configure a webhook, you must specify the triggering event(s) as well as the URL to be notified. When an event occurs in "app A" , the event information is automatically sent to "app B" through the specified URL.
Fusebill supports creating mutliple webhooks, each with a different target URL.
For more information about when and how to use webhooks, see the Fusebill developer documentation.
For step-by-step instructions, see Configure Webhooks.
For the complete list of supported events, see Webhook Events.