ApivomApivom
Get Demo

Telegram Bot API Connector

Telegram's Bot API — send messages, media, locations, polls and documents, manage groups and channels, set webhooks and read updates — registered in Apivom Atlas as 74 routes for tenants that run notifications, alerts or support bots on Telegram with their own bot token.

What you can do

  • Messaging: text, photo, audio, document, video, animation, voice, media groups, location, venue, contact, poll, dice, chat actions
  • Chat management: members, permissions, promotions, invite links, photo, title, description, pinned messages
  • Updates via long polling (getUpdates) or webhook (setWebhook / deleteWebhook / getWebhookInfo)
  • 74 routes on api.telegram.org; the bot token is injected into the /bot{token}/ path and redacted in logs

Use cases

  • Operations alerts in a Telegram group — Post deployment, incident or sales alerts to a team group with send-message and media-group, and pin the ones that matter.
  • Customer notifications without SMS cost — Send order or appointment updates, documents and locations to customers who opted into your bot, with delivery confirmed by Telegram's response.

Telegram's Bot API is the HTTP interface behind every Telegram bot: with a token from @BotFather you can send text and every media type Telegram supports, share locations and venues, run polls, show typing indicators, and administer the groups and channels the bot belongs to — members, permissions, invite links, pinned messages and chat metadata. Incoming messages arrive either by long polling getUpdates or by pointing Telegram at a webhook. Apivom Atlas catalogues 74 of these methods with the credential contract and the AI integration guide (llms.txt); because Telegram puts the token in the URL path, Atlas injects it per request and redacts it in the per-tenant log. No Apivom product workflow uses Telegram today — the connector is available to tenants who run internal alert channels, operations bots or customer notifications on Telegram from their own tooling, and a product workflow is scoped per customer.

Authentication

Your bot token from @BotFather. The Apivom product sends it per request and Atlas injects it into Telegram's /bot{token}/… path, redacting it from logs; Apivom Atlas stores nothing. One token = one bot; create separate bots for separate purposes.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Webhook or polling?

Both are catalogued. Webhooks (setWebhook) push updates to an HTTPS endpoint you control and suit production bots; getUpdates long polling needs no public endpoint and is convenient for internal tools. Only one of the two can be active per bot.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.