How to Create a Grok Bot Telegram With Official Bot API Polling

Last updated: August 30, 2026

This article was produced with AI assistance. Editorial standards apply.

Create a Grok bot Telegram by taking a BotFather token, long-polling getUpdates, calling the xAI Responses API, then posting the reply with sendMessage. Start from the engineering hub if you want typed skill sandboxes next to this transport.

Create the bot account and API keys {#tokens}

Telegram’s FAQ is blunt: you create an account with @BotFather, then you connect a backend over the Bot API. There is no no-code path.

1. Open Telegram. Message @BotFather. Send /newbot.
2. Copy the HTTP token. It looks like 123456:ABC-DEF…. Treat it as a password.
3. Create an xAI key in the console. Export XAI_API_KEY.
4. Export TELEGRAM_BOT_TOKEN. Never commit either value.

The engineering hub lists verified Grok skills you can later hang off this same process. Keep the messenger layer dumb: receive text, call the model, send text.

Long-poll getUpdates without a webhook {#poll-updates}

The Telegram Bot API manual requires HTTPS in the form https://api.telegram.org/bot<token>/METHOD_NAME. Example from that page: …/getMe. GET and POST both work. The JSON envelope always includes boolean ok.

Telegram Bots FAQ states two mutually exclusive receive modes: long polling and webhooks. You cannot long-poll while an outgoing webhook is set. Incoming updates live on Telegram’s servers for at most 24 hours.

getUpdates returns the earliest unconfirmed updates (up to 100). Confirm them by passing offset equal to the last processed update_id + 1. Until you do, the same batch repeats.

Mode	When	Constraint
getUpdates	laptop / staging	fails if a webhook is active
setWebhook	public HTTPS	ports 443, 80, 88, 8443
deleteWebhook	switch back to polling	optional drop_pending_updates

Treat outbound sendMessage like any other mutation: preview in logs first if the bot can post to groups. That is the same dry-run mutation pattern used on CRM writes.

Grok bot Telegram: polling versus webhook {#grok-bot-telegram}

AI Edited

Telegram does not host Grok. A Grok bot Telegram is your process: BotFather token, xAI Responses, sendMessage. The Bot API getting-updates notes state two mutually exclusive receive modes. getUpdates will not work if an outgoing webhook is set. Incoming updates live on Telegram’s servers for at most 24 hours.

Call deleteWebhook before you poll. The Discord counterpart uses a 3-second interaction ACK instead of long polling; see how to build a Grok bot Discord when you ship both clients from one xAI key.

Working sample: sendMessage plus xAI Responses {#working-sample}

AI Edited

Official sendMessage requires chat_id and text (1–4096 characters after entity parsing). The sample below uses only documented HTTPS methods plus the xAI Responses API. Paste into a throwaway directory. Replace chat id after you see your own getUpdates payload.

# 1) Prove the token (official getMe shape)
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getMe"

# 2) Long-poll one batch (timeout seconds; official getUpdates)
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getUpdates?timeout=25"

# 3) Ask Grok (Responses API; recommended over legacy chat/completions)
curl -s https://api.x.ai/v1/responses \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ${XAI_API_KEY}" \
  -d '{"model":"grok-4.6","input":[{"role":"user","content":"Reply in two short sentences."}]}'

# 4) Echo a reply (official sendMessage JSON POST)
curl -s -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage" \
  -H "Content-Type: application/json" \
  -d '{"chat_id": YOUR_CHAT_ID, "text": "BotSkillsStack ping"}'

Minimal Python loop (stdlib only): parse result[], skip non-text, call /v1/responses, POST sendMessage, then getUpdates?offset=<last+1>. Cap text to 4096. Log the tool payload before send—the remote CLI planner skill is a useful sibling when the bot later shells out.

CTA: Run getMe and one getUpdates poll before you write a framework wrapper.

Allowlist chats and graduate to webhooks {#allowlist}

Bots do not see other bots’ messages (loop protection in the FAQ). Privacy mode further limits group traffic. Allowlist chat.id / from.id in your process. Do not let a public group drain your xAI quota.

When you move to production, setWebhook with an HTTPS URL and optional secret_token (header X-Telegram-Bot-Api-Secret-Token). Telegram retries non-2XY webhook responses. You will not receive getUpdates while that webhook exists.

Keep group posts behind an allowlist the same way a personal assistant sandbox should refuse surprise mutations. @xai’s public API thread is about Grok as a developer API, not a hosted Telegram product—you still own the process that calls sendMessage.

FAQ {#faq}

What is a Grok bot Telegram?

Your process: BotFather token, xAI Responses, sendMessage. Telegram does not host Grok. Polling and webhooks are mutually exclusive.

How do I create a Telegram bot with BotFather?

Message @BotFather, send /newbot, copy the HTTP token. That token is the bot<token> path segment on api.telegram.org.

Can I use getUpdates and webhooks at the same time?

No. The FAQ and API notes say they are mutually exclusive. Delete the webhook before polling.

How do I confirm updates so they do not repeat?

Pass offset as the last update_id plus one. Unconfirmed updates are returned again.

How do I send a reply after Grok answers?

POST JSON to /sendMessage with chat_id and text. Truncate to 4096 characters after parsing.

Related reading

Ship the curl path first. Search BotSkillsStack Telegram Grok on Google for adjacent operator guides.

CTA: Confirm getMe, then wire Responses → sendMessage with an allowlist of one chat id.

Sources

• Telegram Bot API
• Telegram Bots FAQ
• xAI Generate text (Responses API)
• xAI Chat Completions (legacy)
• @xai status 1868045124028268983