Two-factor auth

Telegram two-factor authentication for your app

Adding a second factor is the single highest-impact security change most apps can make. Telegram delivery avoids SMS costs and SIM-swap exposure while staying familiar to users.

Where 2FA fits

Trigger a code after the primary credential succeeds, and before you issue a session.

  • Sign-in from a new device or IP
  • Password or email change
  • High-value actions such as payouts or key rotation
  • Admin console access

Implementation sketch

Store the Telegram handle on the user record during enrolment, then reuse it for every challenge.

Send challenge
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" }'

Auditing

Every send and verify is written to the project's authentication log with recipient, outcome and timestamp, so you can investigate suspicious sign-in attempts and export evidence for reviews.

FAQ

Common questions

How is this different from SMS 2FA?

There is no per-message carrier cost and no SIM-swap interception path. Delivery is an encrypted Telegram message from your own bot.

What if a user loses Telegram access?

Keep recovery codes or a second channel. TeleAuth verifies a factor; account recovery policy stays in your app.

Try telegram two-factor authentication with TeleAuth

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

Create free account