member.churned
Subscriber's last active subscription lapsed.
When this fires
A subscriber's last active subscription against the project ends — through expiration, cancellation, or non-payment — and they no longer hold access.
Required ability
project-user:view-any — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "member.churned",
"created_at": "2026-06-18T10:06:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"subscription_id": "sub_01HX...",
"subscriber_id": "usr_01HX...",
"last_plan_id": "pln_01HX...",
"ends_at": "2026-06-18T10:05:00Z"
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always member.churned for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | string ULID | Project this event belongs to. |
data.subscription_id | string ULID | Subscription that lapsed. |
data.subscriber_id | string ULID | Subscriber's project-scoped user id. |
data.last_plan_id | string ULID | Plan id the subscriber was on at churn time. |
data.ends_at | ISO 8601 timestamp | When the subscription ended. |
Caveats
- A subscriber with multiple overlapping subscriptions does not churn until the last one ends.
member.churneddoes not delete the subscriber row; if they re-subscribe later,member.joinedfires for the new subscription.
Related events
subscription.expired— typical predecessor.member.joined— fires if the subscriber returns.- Member events overview — back to family overview.
How is this guide?