> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blindsight.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Logout

> Clear the authentication cookie AND revoke outstanding tokens.

Sessions are stateless JWTs, so clearing the cookie alone left a captured
bearer token valid until expiry. Bumping ``token_valid_after`` (the same
cutoff resolve_user_from_request already enforces) invalidates every token
issued before now for this user.



## OpenAPI

````yaml /api-reference/openapi.json post /api/auth/logout
openapi: 3.1.0
info:
  title: Blindsight API
  version: 0.1.0
  description: >-
    The full Blindsight REST surface, generated from the running application.
    Replace the server host with your own deployment.


    For the Runtime Security integration surface (scan, proxy, tool calls) see
    the Runtime Security spec, which is hand written and carries worked
    examples.
servers:
  - url: https://api.your-blindsight.com
    description: Your Blindsight deployment
security: []
tags:
  - name: Authentication
  - name: Single sign-on
  - name: Social sign-in
  - name: SCIM provisioning
  - name: Projects
  - name: Datasets
  - name: Uploads and imports
  - name: Scans
  - name: Schedules
  - name: Healing
  - name: RAG corpora
  - name: Custom rules
  - name: Playground
  - name: Search and activity
  - name: Apps
  - name: Devices and agents
  - name: Discovery
  - name: DLP policy
  - name: DLP installation
  - name: Compliance
  - name: Audit trail
  - name: Reports
  - name: Export templates
  - name: Workspaces
  - name: Users
  - name: Invitations
  - name: API keys
  - name: Settings
  - name: Directory sync
  - name: Integrations
  - name: Pending actions
  - name: License
  - name: Onboarding
  - name: Support
  - name: Platform operations
  - name: Webhooks
paths:
  /api/auth/logout:
    post:
      tags:
        - Authentication
      summary: Logout
      description: >-
        Clear the authentication cookie AND revoke outstanding tokens.


        Sessions are stateless JWTs, so clearing the cookie alone left a
        captured

        bearer token valid until expiry. Bumping ``token_valid_after`` (the same

        cutoff resolve_user_from_request already enforces) invalidates every
        token

        issued before now for this user.
      operationId: logout_api_auth_logout_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.