Sign in with X.
Modern OAuth-2, not legacy 1.1.

The crypto-native social signal

X handle, profile, and verified status are the strongest social signal in the crypto and creator economies. Asking that audience to sign up with email is friction they will avoid; letting them click Continue with X is conversion. Synq supports X's modern OAuth-2 + PKCE flow, requests the scopes you choose, and issues OIDC tokens — your code does not have to know that X is the inbound provider.

One button, modern protocol underneath

Your code only sees a standard OIDC session. The PKCE plumbing for X happens server-side, in Synq.

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

Get it live

X's developer portal is the most painful step. Synq's side is one screen.

1. 1

   Apply for an X developer account

   Open developer.x.com → Sign up. X requires a developer account for any OAuth integration. The free tier is enough for sign-in flows.
2. 2

   Create a project and an OAuth-2 app

   Inside the developer portal, create a Project, then add an OAuth-2 App under it. Configure User authentication settings → OAuth 2.0 + PKCE. Set the type to Web App or Native App.
3. 3

   Add Synq’s redirect URI

   Add the callback URL Synq displays in Brand → Connections → X. X allows multiple — add one per environment.
4. 4

   Paste credentials into Synq

   Copy the OAuth 2.0 Client ID + Client Secret from X and paste them into Synq. Toggle Enable. Synq encrypts the secret at rest.
5. 5

   Sign in and inspect the user

   Trigger X sign-in. The OAuth consent screen shows your app name. Synq creates a user with the X handle and verified status on the profile.

How X / Twitter support compares

The big difference is OAuth-2 + PKCE versus the legacy OAuth 1.1 most stacks ship. Modern X scopes and refresh tokens depend on the modern flow.

Pair it with

Common questions