API reference / Account

Stop using the workspace's Telegram bot

Troopy stops running the workspace's own bot; people talk to the Chief of Staff through Troopy's shared bot again. Its owner deletes it in @BotFather. Needs an owner or admin.

delete/api/v1/telegram/bot

Authorization

HeaderAuthorization: Bearer <API key>

Or the headerX-API-Key: <API key>

API keyMake one in Troopy under Settings > API keys. It acts as you, in its workspace.

Scopesworkspace:write

Other ways to call it

CLItroopy telegram remove-bot

MCP toolNone. Call it over REST or with the CLI.

Rate limit10 calls in 60 seconds, for each key

RetriesSend an Idempotency-Key header. A retry with the same key gets the first answer back, and the operation runs one time.

Response

200 · application/json

data*object

7 properties

available*boolean

Whether this Troopy has a Telegram bot set up

bot*string | null

The bot's Telegram username

linked*boolean

Whether your Telegram is linked to this workspace

username*string | null

The linked Telegram account's username, if it has one

linkedAt*string | null

workspaceBot*object | null

The workspace's own bot, named after its lead, once someone made it: people talk to the Chief of Staff there

4 properties

username*string

Its Telegram username

disabled*string | null

Why it stopped answering, or null

canOpen*boolean

Whether Telegram lets you open it: its owner and the first 10 others who connected Telegram here

createdAt*string

ISO 8601 date and time

createBotUrl*string | null

Opens Telegram's create-bot screen, filled in with the lead's name: for owners and admins with Telegram linked, while the workspace has no bot

Errors

401 unauthorizedSend an API key as `Authorization: Bearer tr_live_...`. Create one in Troopy under Settings.

403 forbiddenThe key lacks a scope this operation needs, or its owner lacks the role. detail says which; create a key with the scope, or ask an organization owner or admin.

409 conflictThis Idempotency-Key was used for a different request, or that request is still running. Use a new key for a new request.

429 rate_limitedWait the number of seconds in Retry-After, then retry.

Developers

Account

Troop

Skills

Tasks and projects

Needs you

Routines and triggers

Brain

Docs

Canvas

Email

CRM

Outreach

Customers

Analytics

Sessions

Surveys

Support Agent

Tests and incidents

Disputes

Apps