Login OAuth
OAuth callback (POST)
Handle the OAuth provider callback via POST (form data). Used by providers like Apple that use form_post response_mode. Redirects to the client application with a challenge token or error.
POST
OAuth callback (POST)
Path Parameters
The OAuth provider identifier
Example:
"apple"
Body
application/x-www-form-urlencoded
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).
Previous
Initiate SAML login (resolve by email)Start an SP-initiated SAML SSO flow, resolving the connection from the
email's domain. The domain must match exactly one enabled connection's
`email_domain_allowlist`. On success, returns the IdP URL the SDK
navigates the user to; the IdP eventually posts a `SAMLResponse` back to
the connection's [ACS endpoint](/session/api-reference/frontend/saml-acs).
Next
OAuth callback (POST)