Skip to content
Consumer & community

Sign in with Telegram.
Where your community already lives.

The login web3 communities actually use — and the one no major auth platform ships. Synq binds Telegram's hash-verified widget to a per-brand bot token, so your users see your project name on Telegram's authorize screen and your engineers never touch the verification math.

Why it matters

The login crypto-native users expect

Most identity platforms cover Google, Apple, and Microsoft and call the social matrix done. The crypto and gaming communities those platforms ignore mostly live on Telegram. When you ask those users to sign in with Google, you lose them. When you let them sign in with the chat app they already have open, they show up. Synq makes Telegram a first-class connection — same dashboard, same dropdown, same OIDC tokens as every other method.

Bot token
Per brand
Yours, not Synq’s
Verification
HMAC-SHA256
Synq verifies the hash server-side
Lock-in
Zero
OIDC tokens, just like every other method

Drop the button in

The same client-side SDK call you use for every other provider. The only difference is the `provider` argument.

import { SynqProvider, useSynq } from '@synqid/react'
import { SignIn } from '@synqid/react/ui'

export default function App() {
  return (
    <SynqProvider
      issuer="https://api.synq.id"
      clientId={import.meta.env.VITE_SYNQ_CLIENT_ID}
      redirectUri={`${window.location.origin}/auth/callback`}
      theme="dark"
    >
      <Home />
      <SignIn />
    </SynqProvider>
  )
}

function Home() {
  const { signIn } = useSynq()
  return (
    <button onClick={() => signIn({ provider: 'telegram' })}>
      Sign in with Telegram
    </button>
  )
}

Get it live

One-time per brand. Done in five minutes if you already have a Telegram account.

  1. Talk to @BotFather on Telegram

    Run /newbot, give it a name, pick a username. Telegram hands back a bot token. This is the per-brand secret Synq uses to verify sign-ins for your project.
  2. Set the domain on @BotFather

    Run /setdomain on your bot and point it at your sign-in surface (e.g. auth.yourcompany.com or yourcompany.com). Telegram only authorizes sign-ins for domains you have explicitly approved.
  3. Paste the bot token into Synq

    In the Synq Dashboard, open Brand → Connections → Telegram. Paste the bot token and toggle Enable. Synq encrypts it at rest and never exposes it to the browser.
  4. Flip the provider on

    Synq shows Telegram in your default sign-in modal automatically once the connection is enabled. Reorder it in the brand provider list if you want it above Google.
  5. Verify in your app

    Sign in with your own Telegram account. The user appears in the Dashboard with a Telegram connection. Tokens, claims, and webhooks behave exactly like any other provider.

How Telegram support compares

A direct look at which mainstream identity platforms ship Telegram and how.

FeatureClerkWorkOSAuth0PrivySynq
Telegram sign-in shippedCustom only
Per-brand bot token (your name on consent)
Server-side hash verification
Issued as standard OIDC tokens
Pairs with Solana SIWS in the same modal

Pair it with

Common questions

Ship Telegram sign-in your community will use.

Bot token in one screen, brand connection toggled in another, button in your sign-in modal by lunch. Early access is open.