---
title: "Revoke a specific session"
method: DELETE
path: "/auth/sessions/{sid}"
tags: ["Auth"]
---

# Revoke a specific session

`DELETE /auth/sessions/{sid}`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/auth/sessions/{sid}`
- Auth: one of:
  - API key in cookie `mnemom_session`
  - HTTP bearer

Revokes one non-current session by its `sid`. The KV blocklist is updated so the gateway rejects the next request bearing that session on its next hit. Cannot be used to revoke the session making this request — use `POST /auth/sign-out` for that. Requires aal2. Idempotent: a sid that is already revoked or never belonged to the user returns 404 (non-enumeration). See ADR-028.

## Path parameters

- `sid` string, required

## Response `200`

Session revoked.

- object
  - `revoked_at` string, date-time, required

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)