Webhook API notification rules
BILL webhook notifications for events follow a set of rules.
Design | Description |
---|---|
Notification URL | The notification URL is the location where you receive event notifications. The URL that you provide must be HTTPS.
|
All notifications are organization-specific | BILL sends you event notifications only for the BILL organization used to set up a subscription. When you set up a subscription, the |
Event notification | BILL sends each event notification with a unique event |
JSON escaped payload | When BILL sends you an event notification, the Ensure that your integration handles JSON escaped payloads for notifications. See Work with BILL webhooks for more information about a sample payload. |
Order of notifications | In case notifications are sent out of order, organize the notifications based on the timestamp of each notification. |
Time To Live (TTL) | BILL maintains a 180-day event history for each subscription. You can get the list of event notifications sent to you for a subscription with |
Notification retries | When BILL does not receive a HTTP 200 When an event notification fails, BILL tries to send the notification again with exponential backoff - 2 seconds, 4 seconds, 8 seconds, and 16 seconds. When BILL does not receive a HTTP 200 To address any issues with notification retries, you can get the list of event notifications sent to you for a subscription with |
Updated about 22 hours ago