Early bird discounts live! Claim your offer

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

FieldTypeNotes
idstring ULIDUnique event id, prefixed evt_. Use for idempotent processing.
typestringAlways project.bot.disconnected for this event.
created_atISO 8601 timestampServer-side emission time.
api_versionstringWebhook API contract version.
project_idstring UUIDProject this event belongs to.
data.project_idstring UUIDMirrors top-level project_id.
data.bot_idstring UUIDbot 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.connected to follow this event for the replacement bot.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request