Read the result of a sajn Login session
You're viewing API version
2026-09, which is deprecated and stops working on October 1, 2027. To move your integration, see Upgrading to 2026-10.GET
Authoritative read of a login session. Call this from your server after the redirect.
claims and sub are populated only once status is complete, and contain exactly the fields your client is approved for — the same projection the OIDC id_token uses.
sub is stable per person per organization: the same individual logging into any of your clients always yields the same sub, and it can never be correlated with their identifier at another sajn customer.
header
AuthorizationBearer <token>Personal API key, e.g. Authorization: Bearer sajn_sk_.... Not scope-limited — acts as the issuing user.
id*string200
application/json- response
id*stringstatus*stringValue in
"pending""complete""failed""expired"method*string|nullcompletedAt*string|nullstate*string|nullsub*string|nullclaims*|nullcurl -X GET 'https://app.sajn.se/api/v1/login/sessions/string' \ -H 'authorization: string'Example Response
{ "id": "string", "status": "pending", "method": "string", "completedAt": "string", "state": "string", "sub": "string", "claims": { "sub": "string", "amr": [ "string" ], "auth_time": 0, "name": "string", "given_name": "string", "family_name": "string", "birthdate": "string", "nin": "string", "nin_type": "string" }}Was this page helpful?