Passwordless

Passwordless login with Telegram one-time codes

Passwords cause most of your account-recovery tickets and all of your credential-stuffing risk. A Telegram code proves control of an account the user already checks daily, with no password to store, hash or leak.

What changes in your auth flow

The sign-in form collects a Telegram handle instead of a password. Everything after that is two API calls.

  • No password column, no reset emails, no rotation policy
  • Session creation stays entirely in your app — TeleAuth only answers 'is this code valid?'
  • Works as a second factor too, layered on top of an existing password

Verify and create the session

Call verify from your backend. On a true result, mint your own session or JWT exactly as you do today.

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

Keep an escape hatch

Not every user has Telegram. Keep a secondary channel — email codes or an existing password — so account recovery never depends on a single app.

FAQ

Common questions

Is passwordless less secure?

It removes the most commonly attacked credential. Security then depends on the delivery channel, and a Telegram account protected by 2FA is typically stronger than a reused password.

Can I use codes as a second factor instead?

Yes. Send the code after a successful password check and require verification before issuing the session.

Try passwordless login with telegram with TeleAuth

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

Create free account