---
title: "Log Out"
url: "https://nov18-dev.movespot.fyi/apis/konnect-identity-internal-3/versions/4156893f-a5db-4eb8-8deb-93f18fa8fbfa/operations/logout"
---

> Full API specification: https://nov18-dev.movespot.fyi/apis/konnect-identity-internal-3/versions/4156893f-a5db-4eb8-8deb-93f18fa8fbfa.md

# Log Out

`POST` `/logout`

Operation ID: `logout`

Clears the auth cookies.

## Responses

- `201` - Logout response

## OpenAPI definition

```yaml
openapi: 3.0.2
info:
  title: Konnect Identity
  version: 3.0.2
servers:
  - url: https://global.api.konghq.com/v3
    description: Global Base URL
paths:
  /logout:
    post:
      operationId: logout
      summary: Log Out
      description: Clears the auth cookies.
      responses:
        "201":
          $ref: "#/components/responses/LogoutResponse"
      tags:
        - Authentication
security:
  - personalAccessToken: []
  - systemAccountAccessToken: []
  - konnectAccessToken: []
  - clientToken: []
  - serviceAccessToken: []
components:
  responses:
    LogoutResponse:
      description: Logout response
      content:
        application/json:
          schema:
            type: object
            properties:
              login_path:
                description: The login path.
                type: string
            required:
              - login_path
            title: Logout Response
  securitySchemes:
    personalAccessToken:
      type: http
      scheme: bearer
      bearerFormat: Token
      description: >
        The personal access token is meant to be used as an alternative to
        basic-auth when accessing Konnect via APIs.

        You can generate a Personal Access Token (PAT) from the [personal access
        token page](https://cloud.konghq.com/global/account/tokens/) in the
        Konnect dashboard.

        The PAT token must be passed in the header of a request, for example:

        `curl -X GET 'https://global.api.konghq.com/v2/users/' --header
        'Authorization: Bearer kpat_xgfT...'`
    systemAccountAccessToken:
      type: http
      scheme: bearer
      bearerFormat: Token
      description: >
        The system account access token is meant for automations and
        integrations that are not directly associated with a human identity.

        You can generate a system account Access Token by creating a system
        account and then obtaining a system account access token for that
        account.

        The access token must be passed in the header of a request, for example:

        `curl -X GET 'https://global.api.konghq.com/v2/users/' --header
        'Authorization: Bearer spat_i2Ej...'`
    konnectAccessToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >
        The Konnect access token is meant to be used by the Konnect dashboard
        and the decK CLI authenticate with.
    clientToken:
      type: http
      scheme: bearer
      bearerFormat: Token
      description: >
        The Client token is meant to be used by internal service clients for the
        MinK integration.
    serviceAccessToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: |
        The Service access token is meant to be used between internal services.
```
