Telegram login

A Telegram Login Widget alternative built for backends

The official Telegram Login Widget is a script-injected iframe bound to a single domain and bot. TeleAuth gives you the same trust signal — a verified Telegram identity — through a REST API you can call from any backend, on any number of environments.

Where the widget gets in the way

The widget works well for simple websites, but it makes several assumptions that break in real products.

  • One bot is bound to one domain, so staging and preview environments need workarounds
  • The flow only runs in a browser, which rules out mobile apps, CLIs and server jobs
  • Styling is fixed by Telegram, so it rarely matches your design system
  • You still have to validate the hash server-side before trusting anything

The API-first approach

With TeleAuth you own the UI and the flow. Your backend asks TeleAuth to send a code to a Telegram username, then confirms the code the user entered.

Send OTP
curl -X POST https://teleauth.run.place/api/public/v1/otp/send \
  -H "x-api-key: $TELEAUTH_API_KEY" \
  -H "content-type: application/json" \
  -d '{ "username": "ada_lovelace" }'

Multiple environments, one dashboard

Create a separate project per environment — development, staging and production — each with its own bot, API keys, webhooks and logs. Rotating a key in staging never touches production traffic.

FAQ

Common questions

Does this replace Telegram OAuth entirely?

It replaces the widget flow for verifying that a user controls a Telegram account. If you specifically need Telegram profile data returned by the widget, keep using it alongside TeleAuth.

Can I use it in a mobile app?

Yes. Your app calls your backend, and your backend calls TeleAuth with the secret key. The key never ships in the app.

Try telegram login widget alternative with TeleAuth

Create a project, connect your Telegram bot, and send your first OTP in minutes.

Create free account