Skip to main content
The Telegram bot is where you register, so it needs no separate sign-in — the chat is the session. The web terminal and the Chrome extension both sign in to that same account through Telegram’s official login widget.

​
Signing in to the terminal

1

Click Connect

The button is in the top bar. It opens a small Connect dialog.
2

Click Sign in with Telegram

This is the button inside that dialog. A Ballista login page opens in a popup window with Telegram’s login button on it.
3

Authorise in Telegram

The popup hands the session back to the terminal and closes itself, and you land back where you were.

​
Signing in to the extension

Start the sign-in from the extension. The same login page opens, this time in a tab. When you authorise, the tab shows a confirmation and closes; the extension picks up the session and you can go back to what you were doing.

​
You must register in the bot first

The login widget authenticates a Telegram account — it does not create a Ballista one. If you have never sent /start to the bot, the login page tells you exactly that and stops:
Account not found. Please start @<bot handle> in Telegram first, then try again.
The real message names the bot’s actual Telegram handle in place of the placeholder, so it doubles as a pointer to the right bot. Go and create your account, then come back and sign in again. There is no other sign-up path.

​
How long a session lasts

A session is good for 7 days, after which you sign in again the same way. The terminal and the extension hold separate sessions, so signing in on one does nothing to the other and they expire independently. The terminal has a Disconnect button in the top bar that ends its session immediately. The extension has no sign-out control — its session simply runs out after seven days.
Telegram’s authorisation itself is only accepted if it is fresh: a login payload older than 24 hours is rejected. In practice this only matters if you leave the login page open for a day and then click through it.

​
If sign-in fails

  • “Account not found” — you have not registered. Send /start to the bot.
  • The popup was blocked — allow popups for the terminal’s domain and click Connect again.
  • Nothing happens after authorising — close the login window and retry; the token is only ever handed back to the window that opened it, so a stale window cannot complete the handshake.

Web terminal

What you can do once you are in.

Chrome extension

Installing it, and what it adds to Polymarket.