member.resource_added

When this fires

A subscriber gains access to a specific resource (channel, group, supergroup) — either by accepting an invite link or by the bot adding them directly. Each resource grant 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_added",
  "created_at": "2026-05-18T10:05:30Z",
  "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_added` 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 that authorized the grant.
`data.subscriber_id`	string ULID	Subscriber's project-scoped user id.
`data.resource_id`	string ULID	Resource that was granted.
`data.resource_type`	enum: `channel` \| `group` \| `supergroup` \| `manual`	Resource flavour.

Caveats

For paid joins, this event arrives after member.joined and may interleave with other resource events as the dispatcher processes its queue.
Manual perks emit resource_type: "manual" and have no Telegram-side action.

member.resource_removed — paired transition.
member.joined, member.trial_joined — typical predecessors.
Member events overview — back to family overview.