Webhooks
Use BILL webhooks to subscribe to and receive real time notifications for events, such as create a vendor, update a vendor, or create a payment. In addition, as a BILL partner, when you create a subscription for events, you get event notifications for all your created organizations.
Rely onGETAPI operations for accuracy with critical workflowsWhile the BILL webhooks work as expected, we recommend that webhook notifications should not be treated as the only source of truth. BILL sends webhook notifications for a select set of updates.
For critical workflows, we recommend validating data with the
GETAPI operations for accuracy and consistency.
When you subscribe to BILL events, you provide a location URL for where you want to receive notifications. BILL sends a notification to that URL each time a subscribed event is triggered.
In the next set of sections, we walk through the rules for working with BILL webhooks.
| Section | Description |
|---|---|
| Webhook API general rules | Access rules, authentication rules, and idempotent key rules |
| Webhook API notification rules | BILL webhook notifications for events follow a set of rules |
| Work with BILL webhooks | Subscribe to BILL events, generate a test event notification, and get events for a subscription |
| Test with BILL webhook security | Steps for validating the BILL webhook security measures |
| Webhook API error responses | For error responses, BILL sends an HTTP status code depending on the error |
In addition, we list examples of the BILL webhook events and notification payloads in the Notification payloads reference.
Event | Related documentation |
|---|---|
| |
| |
| |
| |
| |
| |
| |
| |
|
Updated about 22 hours ago