project.bot.disconnected
Bot removed or rotated.
When this fires
A creator disconnects the bot from inside the Telegram bot's own /disconnect confirmation flow. Disconnecting from the web dashboard does not emit this event.
Required ability
project:view — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "project.bot.disconnected",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"data": {
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"bot_id": "5e93b1d7-4a20-4c68-8f51-9b0d27e6a34c"
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always project.bot.disconnected 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.project_id | string UUID | Mirrors top-level project_id. |
data.bot_id | string UUID | bot identifier that was just disconnected. |
Caveats
- Disconnecting a bot does not cascade to subscriber resource access — invite-link revocation runs as a separate flow that emits
member.resource_removed. - During a rotation, expect
project.bot.connectedto follow this event for the replacement bot.
Related events
project.bot.connected— paired transition.project.bot.status_changed— health monitoring, probed hourly.- Project events overview — back to family overview.
How is this guide?