member.kicked
Subscriber kicked from a resource without a ban.
When this fires
A creator kicks a subscriber without banning them. The member's status moves to churned, every active subscription is cancelled, and the bot evicts them from every resource they held. The only difference from a ban is that a kick can be reversed by re-subscribing, whereas a ban blocks re-entry until it is lifted.
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.kicked",
"created_at": "2026-05-18T10: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"
},
"reason": "off_topic"
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always member.kicked 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" — a kick moves the member to churned before the event is emitted. |
data.reason | string | null | Reason supplied at kick time. |
Caveats
- A kick evicts the member from every resource their subscriptions granted; expect one
member.resource_removedper resource. - Every active subscription is cancelled in the same flow; expect
subscription.cancelledfor each.
Related events
member.banned— escalation path.member.resource_removed— paired resource event.- Member events overview — back to family overview.
How is this guide?