Chargebee customer_deleted webhook: payload has a subscriptions array, the TS type says singular

TL;DR

Do not trust the chargebee-node TypeScript types for the customer_deleted webhook: the payload carries subscriptions as an array, not a single subscription object.

Steps

1. Do not trust the chargebee-node TypeScript types for the customerdeleted webhook: the payload carries subscriptions as an array, not a single subscription object. If your handler types it as singular, runtime access breaks or silently yields undefined. Type the field as an array of subscription objects on your side and validate against a real event from the dashboard (Logs, Events, the customerdeleted entry, JSON content) rather than the shipped .d.ts.

When to use

You are seeing this: If your handler types it as singular, runtime access breaks or silently yields undefined. Use this skill when you run into "Chargebee customer_deleted webhook: payload has a subscriptions array, the TS type says singular".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Issue chargebee/chargebee-node#96 (closed, 5 comments): The reporter found the TypeScript type for the customer_deleted webhook event declares a singular subscription property while the real incoming webhook body carries a subscriptions array. The Chargebee maintainer first insisted the type was valid, then re-checked against real event logs and admitted the types were wrong and would be fixed.

Verified resolution: Do not trust the chargebee-node TypeScript types for the customerdeleted webhook: the payload carries subscriptions as an array, not a single subscription object. If your handler types it as singular, runtime access breaks or silently yields undefined. Type the field as an array of subscription objects on your side and validate against a real event from the dashboard (Logs, Events, the customerdeleted entry, JSON content) rather than the shipped .d.ts.

Source URL: https://github.com/chargebee/chargebee-node/issues/96