Telegram setup · Help

API keyCommunication & SupportOrg connection

Org-level connection

Telegram is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.

Getting your API key

In Telegram, open @BotFather and send /newbot. Follow the prompts and copy the bot token (it looks like 123456:ABC-...).

Paste that token in the API key field below and click Connect. On Belay stores it encrypted. Do not send the token in chat.

Add the bot to your family group.

If the bot should read group messages (not only commands and replies), send /setprivacy to @BotFather, pick the bot, and choose Disable.

In the group (or a private chat with the bot), send /start. Then call getUpdates — message.chat.id in the result is the chat_id sendMessage needs. Group ids are negative.

The token can call any Bot API method. On Belay's catalog exposes getMe, sendMessage, getUpdates, getChat, getChatMember, setWebhook, deleteWebhook, and getWebhookInfo. There is no inbound webhook receiver yet, so leave the webhook unset and use getUpdates to read replies.

Ready to connect?

Permissions (scopes)

These are the data scopes On Belay can be granted for Telegram. Your org admin controls which scopes are enabled per group.

Scope	Description	Access
`getMe`	Read bot identity	Read only
`sendMessage`	Send messages	Read / Write
`getUpdates`	Poll incoming updates	Read only
`getChat`	Read chat info	Read only
`getChatMember`	Read a chat member	Read only
`setWebhook`	Set the inbound webhook	Read / Write
`deleteWebhook`	Remove the inbound webhook	Read / Write
`getWebhookInfo`	Read webhook status	Read only

Troubleshooting

"Invalid API key" or "Unauthorized" error

Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.

Connected but Claude can't access data

Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.

The key expires or stops working

Some API keys have expiration policies. Generate a new key in Telegram and update it in On Belay → Integrations → Telegram → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.

Still stuck? We're happy to help.

Contact support →