Social

OAuth Account Linking

Link third-party accounts (Discord, GitHub, Google) to your wallet via OAuth 2.0. All flows require an active SIWE session and redirect back to the app on completion.

GET
/api/auth/discord?wallet=0x...
Initiates Discord OAuth 2.0 flow. Redirects to Discord authorization page.
Auth: Session required (wallet must be in session)

Callback at /api/auth/discord/callback handles token exchange and stores the Discord link. Redirects to the app on completion.

302 Redirect to Discord401 No wallet connected403 Wallet not in session
GET
/api/auth/github?wallet=0x...
Initiates GitHub OAuth 2.0 flow. Redirects to GitHub authorization page.
Auth: Session required (wallet must be in session)

Callback at /api/auth/github/callback handles token exchange and stores the GitHub link. Redirects to the app on completion.

302 Redirect to GitHub401 No wallet connected403 Wallet not in session
GET
/api/auth/google?wallet=0x...
Initiates Google OAuth 2.0 flow. Redirects to Google authorization page.
Auth: Session required (wallet must be in session)

Callback at /api/auth/google/callback handles token exchange and stores the Google link. Redirects to the app on completion.

302 Redirect to Google401 No wallet connected403 Wallet not in session

Note: These OAuth flows are browser-based redirects. They cannot be used directly from SDK or agent contexts — use the tweet verification flow for programmatic X account linking.