member.resource_added

When this fires

Subscriby mints a join-request invite link for a subscriber on one of the resources their subscription grants, and attaches it to the subscription. Each resource grant emits its own event. The event marks the grant, not the subscriber's arrival — they may not have opened the link yet.

Required ability

project-user:view — 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": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
  "data": {
    "subscription_id": "5b7e2d40-1a86-4c39-97f2-e83d0b16c5a4",
    "subscriber_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",
    "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",
    "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 UUID	Project this event belongs to.
`data.subscription_id`	string UUID	Subscription that authorized the grant.
`data.subscriber_id`	string UUID	Subscriber's project-scoped user id.
`data.resource_id`	string UUID	Resource that was granted.
`data.resource_type`	enum: `channel` \| `group` \| `supergroup`	Resource flavour.

Caveats

Ordering against the join event is not guaranteed: the dispatcher is queued before member.joined is emitted on the access-code path, and paid joins emit no member.* join event at all. Treat resource events as independent.
Manual (non-Telegram) resources never emit this event — the dispatcher only walks resources with a linked Telegram chat.

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