member.kicked
Subscriber kicked from a resource without a ban.
When this fires
A subscriber is removed from one or more resources without being banned — typically a corrective action that does not strip them of all project 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.kicked",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"subscriber": {
"id": "usr_01HX...",
"telegram_user_id": "123456789",
"status": "customer"
},
"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 ULID | Project this event belongs to. |
data.subscriber.id | string ULID | Subscriber's project-scoped user id. |
data.subscriber.telegram_user_id | string | Telegram user id. |
data.subscriber.status | string | Subscriber's overall status — typically unchanged from customer. |
data.reason | string | null | Reason supplied at kick time. |
Caveats
- A kick is resource-scoped from the subscriber's perspective; expect
member.resource_removedfor each resource the kick covers. - Subscriptions are not cancelled by a kick.
Related events
member.banned— escalation path.member.resource_removed— paired resource event.- Member events overview — back to family overview.
How is this guide?