Skip to main content
The session endpoints let you inspect your current authenticated session and log out by revoking it. When you log out, the server invalidates the session record and instructs the browser to clear the session cookie — any further requests using that cookie will receive a 401 response.

Inspect the Current Session

Before logging out you can call GET /auth/session to confirm the session is active and retrieve basic profile information.

Endpoint

Requires an active session cookie. No CSRF token is needed for read-only requests.

Example Request

Success Response — 200 OK

object

Log Out — Revoke Current Session

Endpoint

Requires an active session cookie. Because this is a state-changing DELETE request, you must first obtain a CSRF token via GET /auth/csrf-token and pass it in the x-csrf-token header.
The server returns 204 No Content even if the session was already revoked or expired. This idempotent behaviour means it is safe to call the endpoint more than once without worrying about error handling for already-logged-out sessions.

Example Request

Success Response — 204 No Content

The session is revoked and the session cookie is cleared. The response body is empty.

Error Responses

Example 401 Response

List All Sessions

View every active session across your devices and revoke any of them.

Log In

Start a new session after logging out.