Skip to content
Consumer & community

Sign in with Discord.
Where the community lives.

For gaming guilds, NFT projects, creator economies, and any app where the user's Discord identity is the one they actually care about. Synq ships Discord as a first-class connection with per-brand credentials and optional server-role lookup, behind standards-compliant OIDC tokens.

Why it matters

The identity gamers and crypto users actually use

Asking a gamer or a member of a web3 community to sign up with an email they barely check is the highest-friction onboarding you can ship. Discord is where they already are, and their Discord profile is the identity they think of as theirs. Synq wires Discord OAuth-2 as a first-class connection and can optionally fetch the user's guild membership on sign-in — useful if your access model depends on server roles.

Server roles
Optional fetch
Authorize on Discord roles
Credentials
Per brand
Your Discord app, not Synq’s
Token format
Standard OIDC
No Discord-specific SDK on your side

One button, three stacks

The same SDK call you use for every other provider — only the provider string changes.

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: 'discord' })}>
      Continue with Discord
    </button>
  )
}

Get it live

Mostly clicking in the Discord developer portal. The Synq side is one screen.

  1. Create an application in the Discord developer portal

    Open Discord Developer Portal → New Application. Give it your brand name. Discord shows you a Client ID and lets you generate a Client Secret.
  2. Add Synq’s redirect URI

    Under OAuth2 → Redirects, add the callback URL Synq displays in Brand → Connections → Discord. Discord requires an exact match.
  3. Paste credentials into Synq

    In the Dashboard, open Brand → Connections → Discord. Paste the Client ID + Client Secret and toggle Enable. Synq encrypts the secret at rest.
  4. Pick scopes

    By default Synq requests `identify email`. Add `guilds` if you need the user’s server list, or `guilds.members.read` for in-server role lookup. Each adds a line to the consent screen.
  5. Test on your own Discord account

    Trigger Discord sign-in. The consent screen shows your brand name. Synq creates the user and stores the Discord username and avatar URL on the profile.

How Discord support compares

Some platforms support Discord as a custom OAuth connection — meaning you do the wiring. Synq ships it as a first-class provider.

FeatureClerkWorkOSAuth0Synq
Discord sign-in shipped first-classCustomCustom
BYO Discord credentials per brandPer app
Server-role lookup on sign-in
Issued as standard OIDC tokens
Pairs with Telegram + Matrica in one modal

Pair it with

Common questions

Onboard the community where they already are.

Discord app in their developer portal, paste into Synq, button in your sign-in modal — that’s the whole integration. Early access is open.