/auth/login-ssoSign in with single sign-on
Exchanges an identity provider's ID token for a SQRL access token, creating the account on first use if no account matches the identity.
Use this route when your organisation signs members in through a federated identity provider. Obtain an ID token from the provider in your own client, then pass it through unchanged. If no SQRL account matches the identity in the token, the call registers one, so the same request covers both a first sign-in and every later one.
The response carries the access token directly. It has no requires_2FA field,
so there is no second step on this route. As with
POST /auth/login, a secure refresh cookie is set through
Set-Cookie; keep it, along with uid and sid, for
POST /auth/refresh. The user_info object is the User
shape described in Shared objects.
idTokenstringrequired#What happens next
Send token as a bearer token on every later call, and refresh it with
POST /auth/refresh before it expires. Where this call
registered the account rather than matching an existing one, check
OrganisationsInfo: an account that belongs to no organisation yet either waits
for a workspace invitation or submits
POST /api/v1/request-organisation.