member.removed

When this fires

A creator manually removes a subscriber from the project. The subscriber is soft-deleted, their access is revoked, and any active subscription is cancelled.

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.removed",
  "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": "removed"
    },
    "reason": "creator_manual"
  }
}

Field reference

Field	Type	Notes
`id`	string ULID	Unique event id, prefixed `evt_`. Use for idempotent processing.
`type`	string	Always `member.removed` 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, if the subscriber is Telegram-linked.
`data.subscriber.status`	string	Subscriber's new status post-removal.
`data.reason`	string \| null	Reason supplied by the creator at removal time.

Caveats

Distinct from a ban: removed subscribers can rejoin, banned subscribers cannot. See member.banned.
Distinct from a kick: a kick targets a single resource without removing the subscriber. See member.kicked.

member.banned, member.kicked — alternative discipline events.
subscription.cancelled — fires alongside if there was an active subscription.
Member events overview — back to family overview.