member.unbanned
Ban lifted; subscriber returns to churned status.
When this fires
A creator lifts a previously applied ban. The subscriber returns to a churned state — they can re-subscribe, but they do not automatically regain access to past subscriptions.
Required ability
project-user:view — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "member.unbanned",
"created_at": "2026-05-22T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"data": {
"subscriber": {
"id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",
"telegram_user_id": null,
"status": "churned"
}
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always member.unbanned for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | string UUID | Project this event belongs to. |
data.subscriber.id | string UUID | Subscriber's project-scoped user id. |
data.subscriber.telegram_user_id | null | Always null — the Telegram id is not an attribute of the member record. |
data.subscriber.status | string | Always "churned" for this event. |
Caveats
- Unbanning does not restore prior subscriptions; the subscriber must purchase a new one to regain access.
- A subsequent purchase fires
subscription.activated; only an access-code redemption firesmember.joined.
Related events
member.banned— paired transition.subscription.activated— fires if the subscriber repurchases.- Member events overview — back to family overview.
How is this guide?