Revoke my session
Logs out by permanently deleting the session. The `__nextgen_session` cookie issued at creation (or superseded by a handoff exchange) is required. Idempotent: if the session is already gone this still returns 204. Any tokens derived from the session are invalidated, and the cookie itself is cleared in the response.
Logs out by permanently deleting the session.
The __nextgen_session cookie issued at creation (or superseded by a handoff
exchange) is required. Idempotent: if the session is already gone this still
returns 204. Any tokens derived from the session are invalidated, and the
cookie itself is cleared in the response.
Authorization
nextgenSession The __nextgen_session cookie issued at session creation or superseding handoff exchange.
A missing or invalid cookie yields 401 with code auth.unauthorized and the message
Missing or invalid session token.
In: cookie
Response Body
application/json
application/json
curl -X DELETE "https://example.com/sessions/me"{ "message": "string", "details": {}, "code": "auth.unauthorized"}{ "code": "auth.unauthorized", "message": "The request lacks valid authentication credentials."}Query sessions POST
Returns the sessions of a project, paginated with a cursor. Sessions of every lifecycle state are returned; each carries its `state`. Requires `session.read` permission.
Revoke session DELETE
Permanently deletes the session, terminating it immediately. This is the operator revoke path and requires the `session.delete` scope on a project-bound credential. End-user logout with the `__nextgen_session` cookie is `DELETE /sessions/me` (`nextgenSession` scheme). Idempotent: deleting a session that does not exist (or was already deleted) still returns 204. After deletion, any tokens derived from the session are invalidated.