Webhooks
Use the 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.
IMPORTANT
While 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
GET
API 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. You can jump to Working with BILL webhooks to learn about examples for working with the webhooks API.
In addition, we list examples of the BILL webhook events and notification payloads in the Notification payloads reference.
Event | Related documentation |
---|---|
bill.created bill.updated bill.archived bill.restored | Bill notification payloads |
vendor.created vendor.updated vendor.archived vendor.restored | Vendor notification payloads |
autopay.failed | Vendor auto-pay notification payloads |
payment.updated payment.failed | Payment notification payloads |
bank-account.created bank-account.updated | Bank account notification payloads |
card-account.created card-account.updated | Card account notification payloads |
risk-verification.updated | Risk verification notification payloads |
spend.transaction.updated | Spend & Expense transaction notification payloads |
Updated 8 days ago