Login webhooks
Get notified when a sajn Login authentication completes or fails
Two events tell you the outcome of a login without waiting for the browser to come back.
| Event | Fires when |
|---|---|
login.completed | A user finished authenticating |
login.failed | A login ended in a state the user can't retry out of |
They use the same webhook system as the rest of sajn: the same event body, Standard Webhooks
signing, retries, and delivery log. To receive them, add login.completed and login.failed to
the events of a webhook. For setup, see Webhooks.
Why you might want them
The normal flow is synchronous: the user is redirected back and you exchange the code. Webhooks matter for the case that redirect never arrives.
The common one is mobile. A user opens the login in an in-app browser, authenticates, and closes the browser before it redirects. They believe they logged in; your app never heard anything.
sajn completes the authentication server-side regardless — a background watchdog finishes the flow if the browser stops responding — so the result exists. The webhook is how you learn about it.
If you use OpenID Connect, a login.completed webhook can't be exchanged for an
id_token — the authorization code goes to the browser and expires in 60 seconds. Treat the
webhook as a signal to prompt the user to try again, or to reconcile your own records. With the
Session API you can act on it directly: GET the session for the claims.
login.completed
{
"id": "cm4k2x9p10001abcd1234efgh",
"type": "login.completed",
"createdAt": "2026-10-02T12:03:45.000Z",
"apiVersion": "2026-10",
"workspaceId": "cm4k2x9p10002abcd1234efgh",
"environment": "PRODUCTION",
"actor": null,
"data": {
"object": {
"id": "cm4k2x9p10003abcd1234efgh",
"sessionId": "kZ8f3cQpL7vR3mN8tYw4bZc1dH6jS0aEuGiKoPqTrUv",
"clientId": "cm4k2x9p10004abcd1234efgh",
"mode": "SESSION",
"method": "SE_BANKID",
"sub": "clx7f2k9v0001abcdefghijkl",
"authenticatedAt": "2026-10-02T12:03:45.000Z",
"state": "your-internal-reference"
}
}
}The fields of data.object:
| Field | Meaning |
|---|---|
id | The authentication record, which is also what you're billed for |
sessionId | The login session. With the Session API, use it to read the claims |
clientId | The sajn Login client that started the login |
mode | OIDC or SESSION |
method | The eID method, SE_BANKID |
sub | The pseudonymous subject, the same value your id_token carries |
authenticatedAt | When the user authenticated |
state | Your own value from the login request. Absent if you didn't send one |
The payload deliberately contains no identity. No name, no personnummer — only the
pairwise sub. A webhook body lands in your logs and every proxy between us, so the claims stay
behind an authenticated read.
login.failed
{
"id": "cm4k2x9p10005abcd1234efgh",
"type": "login.failed",
"createdAt": "2026-10-02T12:08:12.000Z",
"apiVersion": "2026-10",
"workspaceId": "cm4k2x9p10002abcd1234efgh",
"environment": "PRODUCTION",
"actor": null,
"data": {
"object": {
"sessionId": "kZ8f3cQpL7vR3mN8tYw4bZc1dH6jS0aEuGiKoPqTrUv",
"clientId": "cm4k2x9p10004abcd1234efgh",
"mode": "SESSION",
"reason": "expiredTransaction",
"failedAt": "2026-10-02T12:08:12.000Z",
"state": "your-internal-reference"
}
}
}data.object has the same sessionId, clientId, mode, and state as login.completed,
plus reason, the BankID hint code, and failedAt.
This fires only for terminal failures. Recoverable ones — the user cancelled, the QR failed to scan, the app was not found — do not fire, because the login page offers a retry within the same session and notifying on each would flood your endpoint.
Typical reason values are expiredTransaction and certificateErr. For the full list, see
Errors.
Delivery
Login events are delivered like every other sajn event: signed according to Standard Webhooks, retried with backoff, and visible in the delivery log on the Webhooks tab in Konsol.
Two rules worth repeating:
- Verify the signature with the
webhook-id,webhook-timestamp, andwebhook-signatureheaders before you act on an event. See Verify signatures. - Expect duplicates. Deliveries are at-least-once. The event
idis stable per event, anddata.object.idonlogin.completedis stable per authentication. Use either as an idempotency key.
Never treat a webhook as an authentication in itself. It says an authentication happened; it is not a credential and does not establish a session for whoever is holding a browser. Bind the session through the redirect, or through the Session API read.
Was this page helpful?
Last updated on