Chargebee Webhooks: Send Billing Events to Sazabi

Webhook facts checked on the platform’s docs on Nov 8, 2026.

Chargebee records every change on your billing site as an event: a subscription starts, an invoice is generated, a payment fails. A webhook sends those events to a URL as they happen. This page covers the payload and how to keep the events in Sazabi.

What Chargebee sends

Chargebee names events in lowercase with underscores. Examples are subscription_created, subscription_cancelled, subscription_activated, invoice_generated, payment_succeeded, payment_failed, payment_refunded, customer_created and payment_source_expiring. The events reference lists the full set.

Each call is an HTTP POST with content type application/json. The body is the event: an id, occurred_at, source, event_type, api_version and a content object. The content object holds the affected resources, so a subscription event includes the subscription and usually the customer.

Why send it to Sazabi

Billing events explain customer-visible behavior. A burst of payment_failed events, a wave of subscription_cancelled after a release or an invoice_generated that never arrived all matter when you debug an incident. Sazabi's Webhook Events source stores each JSON payload as a searchable log record, with the payload under webhook.* attributes, so those events sit next to your application logs.

Chargebee gives each webhook its own URL, which makes path suffixes easy. Use /chargebee for one webhook, or /chargebee/payments and /chargebee/subscriptions for several. Sazabi stores the suffix as webhook.path.

Set it up in Chargebee

1. Go to Settings, then Configure Chargebee, then API Keys and Webhooks. Open the Webhooks tab.
2. Select Add Webhook. You can create up to five.
3. Enter a webhook name and your Sazabi intake URL with a suffix.
4. Leave Protect webhook URL with basic authentication off. The intake URL is the credential.
5. Under Events to Send, select the events you want. All events are selected by default, so narrow the list.
6. Save, then select Test Webhook on the webhook card, choose an event and select Test URL. Chargebee shows the request, the response status and the response.

Chargebee has test sites and live sites. Create the webhook on each site you want to observe. On a test site, an unused webhook gets a deactivation notice by email and is deactivated if you take no action.

Example payload

An abbreviated event using attributes from the Chargebee docs. It is an example, not a captured delivery.

{
  "id": "ev_16BPgETyVrQbiGhA",
  "occurred_at": 1702645601,
  "source": "admin_console",
  "object": "event",
  "api_version": "v2",
  "event_type": "subscription_created",
  "content": {
    "subscription": {
      "id": "16BPgETyVrQVHGh1",
      "customer_id": "sarah",
      "status": "active",
      "resource_version": 1702645601793
    },
    "customer": { "id": "sarah" }
  }
}

In a Sazabi thread, search for a top-level field such as webhook.event_type to isolate one event type. The event id is a good key for finding duplicates.

What to watch for

• Retries and duplicates. Chargebee notes that webhooks can be delivered more than once because of retries and says to deduplicate on the event id. The payload doesn't change on a retry.
• Order. Events can arrive out of order. resource_version on the resource increases with each change, so compare it rather than arrival time.
• Stale snapshots. A payload is a point-in-time snapshot taken right after the change. By the time you read it, the resource may have moved on.
• Timeouts. On a live site Chargebee waits up to 20 seconds to connect, 20 seconds to read and 60 seconds for the whole call. Test sites allow 10, 10 and 20.
• Event volume. With All Events selected, a busy site can produce many records. Choose the events you will search.
• Personal data. Events include customer email addresses and masked card details. An Exclude card information option exists on the webhook.

The Intake page in the Sazabi dashboard shows ingestion volume per source.

Retries

Chargebee treats any 2XX status as success. A failed call is retried up to seven times: two minutes after the failure, then six minutes, 30 minutes, one hour, five hours, one day and two days after the previous retry. You can also resend an event from Logs, then Events in the Chargebee console. Chargebee documents basic authentication rather than HMAC signatures.

For store orders that feed the same billing system, see Shopify. For CRM changes around the same customers, see HubSpot.