API reference
Telegram alert channel status
telegram_status — Whether the workspace's own Telegram bot is set up: enabled, bot username, chat set, last verified / sent, last error.
telegram_status · Reads saved data
Whether the workspace's own Telegram bot is set up: enabled, bot username, chat set, last verified / sent, last error. Never returns the bot token.
| REST | GET /api/public/v1/telegram |
| MCP tool | telegram_status |
| Permission needed | view — Owner, Manager, Operator, Viewer |
| Scope group | infra:read |
| Group | VPS, proxies and alerts |
| Shown up front in profiles | Infrastructure |
Input
No input.
Result
Returned in the { data, meta } envelope, without creating a job on X. Lists include next_cursor and has_more.
Example
Call over REST
curl -X GET "https://reach-link-craft.lovable.app/api/public/v1/telegram" \
-H "Authorization: Bearer $XBUDDY_API_KEY"
Call over MCP
{
"method": "tools/call",
"params": {
"name": "telegram_status",
"arguments": {}
}
}
Errors you may get
| Code | HTTP | Retryable |
|---|---|---|
unauthorized |
401 | No |
key_expired |
401 | No |
integration_revoked |
401 | No |
connection_not_linked |
403 | No |
integration_paused |
403 | No |
workspace_integrations_paused |
403 | No |
integration_authorization_lost |
403 | No |
workspace_suspended |
403 | No |
forbidden |
403 | No |
invalid_input |
422 | No |
rate_limited |
429 | Yes |
internal |
500 | Yes |