Skip to main content
These events track the lifecycle of a fan’s profile subscription to a creator, independently of the money movement. They are the successor to the legacy subscription.new, subscription.cancelled, and subscription.expired events. Requires the read:creator scope. Delivered in the Standard-Webhooks envelope; the fields below describe the data object.
A typical churn sequence is cancel_at_period_end_changed (auto-renew off, access continues) followed by deactivated when the paid period runs out. A failed renewal can deactivated a subscription with no prior cancel_at_period_end_changed. Native profile subscriptions have no external id — the subscription’s identity is the (purchaser, creator) pair.

Subscription resource

Example: creator.subscription.activated

Example: creator.subscription.deactivated

The creator.subscription.cancel_at_period_end_changed event uses the same resource shape with cancel_at_period_end reflecting the new state (true when auto-renew was turned off, false when turned back on) and status still active.