How to get a token from a Telegram bot

• @BotFather → /mybots.
• Pick the bot.
• Open something like API Token.
• Use Revoke / “revoke current token” (labels shift sometimes). You’ll get a fresh token.
• Save it somewhere sensible, then update every integration that had the old one.

Minimal Python example

pip install python-telegram-bot

from telegram import Update
from telegram.ext import ApplicationBuilder, CommandHandler, ContextTypes

TOKEN = "YOUR_TOKEN_FROM_BOTFATHER"

async def start(update: Update, context: ContextTypes.DEFAULT_TYPE):
    await update.message.reply_text("Hello! The bot is up and running.")

app = ApplicationBuilder().token(TOKEN).build()
app.add_handler(CommandHandler("start", start))

app.run_polling()

No time for code?

Telegram bot in BOT-MARKET

BOT-MARKET is a visual builder: templates and blocks instead of repos. Pick a flow, hook up your bot, tweak copy and buttons, tweak conditions, ship.

Prerequisite: bot already exists in @BotFather and you’re holding the API token. Then you’re ready inside BOT-MARKET.

1. Step 1. Open the bot catalog

   Log into BOT-MARKET → Bot Catalog. You’ll see templates: bare bones, leads, mandatory channel checks, and more.

2. Step 2. Pick a template

   Match the card to what you’re building, then hit Create on that card.

   Need subscription checks? Grab Mandatory Channel Subscription Bot — it’s the usual starting point for that job.
3. Step 3. Open the connect / clone screen
   

   Bot asks the user to subscribe to the listed channels.

   The next screen explains what the template does and gives you a field to attach your Telegram bot.

4. Step 4. Paste your bot token

   In the “Bot token” field, paste the API token that you received earlier from @BotFather.

   Paste the token exactly — no spaces, no quotes. Otherwise BOT-MARKET won’t bind the bot.
5. Step 5. Clone

   Token in place → Clone selected bot.

   If the token’s valid, you get your own copy wired to your bot; it lands in the workspace ready to edit.

6. Step 6. Tweak copy and flow

   Rename messages, reorder buttons, tighten conditions — whatever the template left open for you.

   BOT-MARKET shows the flow as a diagram. You see branches, user paths, and what fires when — handy when the scenario isn’t linear.
7. Step 7. Wire channels if the template needs them

   Subscription or join-request flows mean adding the bot to the right channel/chat with the admin rights the template asks for.

Token in, bot on BOT-T

Token from @BotFather in hand → open BOT-T, head to bot creation, then:

1. Copy the token

   BotFather’s message has the API string; copy it whole, no trimming.

2. Open BOT-T

   In your account, open the “new bot” / create flow (wording shifts, but it’s the obvious entry).

3. Paste the token

   There’s a dedicated field — drop the BotFather value there.

4. Confirm creation

   Hit Create bot or whatever the UI labels the final step.

5. Wait for the handshake

   Good token → bot shows up in your BOT-T workspace; then you edit behavior, not credentials.

Messages and logic

What you configure next tracks what you’re building.

Rough map:

• Store — catalog, categories, cards, payments, checkout steps.
• Leads — greeting, intake, confirm buttons, follow-up branches.
• Support — topics, routing, who picks up the thread, ticket-style handling.

Fine-tuning after connect

A lot of “my bot is broken” tickets trace back to launch details, not the template itself. Usual suspects:

• Bad or stale token.
  Typo, half copy-paste, or you revoked it and forgot to update the builder — the platform simply can’t talk to Telegram.
• Bot isn’t admin where it matters.
  Sub checks and join flows need real permissions in the channel or group.
• Wrong invite link flavor.
  Join-request flows need the link type that actually asks for approval — a plain public link won’t behave the same.
• Demo text and demo IDs still in the clone.
  Especially on BOT-MARKET: the bot “runs” but points at sample channels or placeholder copy.
• Never walked through as a user.
  Designer view looks fine; real account hits a dead branch. Click your own links once.

Recover the account first

Best case: you get the old login back and keep the same bot + subscribers. Try in this order:

• Phone login — SMS or Telegram-delivered code on the number tied to the account.
  
• 2FA backup codes if you enabled two-step verification.
  
• Telegram support — telegram.org/support. Explain the number, roughly when access dropped, what devices still show the session. Heads-up: they don’t guarantee recovery without solid proof it’s yours.

If the account is gone for good

Before disaster strikes

Second Telegram login with a spare channel or backup bot gives you a place to point traffic if the main profile vanishes or gets limited.

Audience insurance

Some teams run a small lead-capture bot on that backup account and funnel everyone there too, so one lost phone number doesn’t erase the whole contact base. Starter flow: spin up a lead bot.