Bunny Com Webhooks

generated: '2026-11-03'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.bunny.com/developer/webhooks/webhooks
sources:
- https://docs.bunny.com/developer/webhooks/webhooks
- https://docs.bunny.com/developer/webhooks/webhook-security
- https://docs.bunny.com/developer/webhooks/tenant-provisioning-change
- https://docs.bunny.com/developer/webhooks/checkout-validation
description: 'Bunny provides two webhook event types:'
events:
- event: Tenant provisioning change
  description: Sent when a subscription changes (activated, cancelled, trial extended, quote applied, tenant linked, or plan features changed)
    to keep SaaS tenants in sync with their subscription.
- event: Checkout validation
  description: Sent while a user builds or edits a checkout, at checkout time, or on signup, to let the platform approve or deny a plan or quantity
    change before payment is taken.
delivery:
  auth: Bearer token set as a Webhook auth token and sent in the Authorization header.
  signature: HMAC‑SHA1 of the request body using the Webhook signing key, placed in the x-bunny-signature header.
note: Both platform and workflow webhooks use the same auth token and signing key mechanisms; the Checkout validation webhook includes the signature
  but does not include the auth token.
docs: https://docs.bunny.com/developer/webhooks/webhooks