Login OAuth
OAuth callback (GET)
Handle the OAuth provider callback via GET (query parameters). Redirects to the client application with a challenge token or error.
GET
OAuth callback (GET)
Path Parameters
The OAuth provider identifier
Example:
"google"
Query Parameters
The authorization code from the OAuth provider
Example:
"4/0AX4XfWh..."
The state parameter for CSRF protection
Example:
"st_01jqebhswje1ka1z7ahr9rfsgt"
Error code from the OAuth provider
Example:
"access_denied"
Error description from the OAuth provider
Example:
"The user denied access"
Response
Redirect to the client application's redirect_uri with one of:
challenge_token=<jwt>— login may be finalized via the Finalize login endpoint.challenge_token=<jwt>&status=otp_required— the OAuth provider hasverify_email=trueand the IdP returned an unverified email. The SDK sends an email OTP and the host app must collect the code via the OTP screen; the SDK finalizes the login automatically once the OTP is verified.error=<code>&error_description=<message>— provider error or Session-level rejection (e.g.email_already_in_use).
OAuth callback (GET)