member.banned

When this fires

A creator bans a subscriber. Their access is revoked, the bot kicks them from all linked resources, and they cannot re-join the project until the ban is lifted.

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.banned",
  "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": "banned"
    },
    "reason": "spam"
  }
}

Field reference

Field	Type	Notes
`id`	string ULID	Unique event id, prefixed `evt_`. Use for idempotent processing.
`type`	string	Always `member.banned` 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 of the banned subscriber.
`data.subscriber.status`	string	Always `"banned"` for this event.
`data.reason`	string \| null	Reason supplied at ban time.

Caveats

Bans persist across subscription cycles until explicitly lifted via member.unbanned.
Active subscriptions are cancelled in the same flow; expect subscription.cancelled.

member.unbanned — paired transition.
member.kicked — softer discipline (resource-scoped).
Member events overview — back to family overview.