member.resource_removed
Subscriber loses access to a specific resource.
When this fires
A subscriber's access to a specific resource is revoked — through subscription expiry, a pause, a kick, or an explicit unlink. Each resource revocation emits its own event.
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.resource_removed",
"created_at": "2026-06-18T10:06:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"subscription_id": "sub_01HX...",
"subscriber_id": "usr_01HX...",
"resource_id": "rsr_01HX...",
"resource_type": "channel"
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always member.resource_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.subscription_id | string ULID | Subscription whose grant was revoked. |
data.subscriber_id | string ULID | Subscriber's project-scoped user id. |
data.resource_id | string ULID | Resource the subscriber lost access to. |
data.resource_type | enum: channel | group | supergroup | manual | Resource flavour. |
Caveats
- Multiple revocations for the same subscriber typically arrive in close succession when a subscription expires; use
MP-Event-Idfor dedupe. - A revocation against a
manualresource indicates the perk was withdrawn but does not interact with Telegram.
Related events
member.resource_added— paired transition.subscription.expired,subscription.paused,member.kicked— typical triggers.- Member events overview — back to family overview.
How is this guide?