Logout — POST /api/v1/auth/logout
Logout
Server-side logout — revokes the caller’s access-token jti until its natural expiry and revokes all live refresh tokens for the user so the session cannot be re-minted via /auth/refresh.
Endpoint: POST /api/v1/auth/logout
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
204 | Successful Response | No body |
422 | Validation Error | HTTPValidationError (application/json) |
204 returns no body.
Errors this endpoint returns, read from its source code:
503, with the message “Token revocation store unavailable; logout was not applied”
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Authentication
- Operation ID:
logout_api_v1_auth_logout_post - Source code:
backend/app/routers/auth.py, line 871 - Specification: OpenAPI JSON