Provider-specific OAuth callback (GET)
Client
Provider-specific OAuth callback (GET)
OAuth callback endpoint for provider-specific flows (most providers use GET).
Response varies based on the original OAuth initiation:
- With code_challenge (PKCE): Redirects with
insforge_codefor exchange endpoint - Without code_challenge (web): Redirects with
access_tokenand sets httpOnly cookie
GET
Provider-specific OAuth callback (GET)
Documentation Index
Fetch the complete documentation index at: https://docs.insforge.dev/llms.txt
Use this file to discover all available pages before exploring further.
Path Parameters
Available options:
google, github, discord, linkedin, facebook, instagram, tiktok, apple, x, spotify, microsoft Query Parameters
Authorization code from OAuth provider
JWT state with redirect URI and optional code_challenge
Direct ID token (for some providers)
Response
302
Redirect to application.
- PKCE flow: redirect_uri?insforge_code={code}&user_id={id}&email={email}&name={name}
- Web flow: redirect_uri?access_token={token}&user_id={id}&email={email}&name={name}&csrf_token={csrf}