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

# Revoke Session

> Revoke one of the logged-in user's own dashboard sessions.

Deletes a single session belonging to the logged-in user, signing that device
out immediately. Find session IDs with
[List Sessions](/api-reference/auth/list-sessions). A session that does not
exist (already revoked or purged), or belongs to another user, returns `404` —
ownership is never disclosed. Expiry is not checked here: a session that has
expired but not yet been purged is deleted and returns `200` like any other. To
sign out everywhere except the current device, use
[Revoke Other Sessions](/api-reference/auth/revoke-other-sessions).

Requires a logged-in user session; API-key callers receive `401`.

## Path Parameters

| Parameter | Type          | Required | Description                             |
| --------- | ------------- | -------- | --------------------------------------- |
| `id`      | string (uuid) | Yes      | The session to revoke (path parameter). |

## Example Request

```bash theme={null}
curl -X DELETE https://api.recurso.dev/v1/auth/sessions/5c0e2b17-93da-4f61-b8a4-7e1f6d3c9b20 \
  -b cookies.txt
```

## Example Response

```json theme={null}
{
  "message": "session revoked"
}
```

## Errors

| Status | Code                | When                                                                                                  | Fix                                                                                           |
| ------ | ------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| 400    | `validation_failed` | `id` is not a valid UUID.                                                                             | Pass a session `id` from [List Sessions](/api-reference/auth/list-sessions).                  |
| 401    | `unauthorized`      | No live session cookie, or the caller authenticated with an API key rather than a user session.       | Sign in via [`/auth/login`](/api-reference/auth/login) and send the `recurso_session` cookie. |
| 404    | `not_found`         | The session does not exist (including one already revoked or purged), or belongs to a different user. | Refresh the list; the session may already be gone.                                            |
| 500    | `internal_error`    | The session could not be deleted.                                                                     | Retry; contact support if it persists.                                                        |

Errors use the standard envelope — see [Errors](/api-reference/errors).


## OpenAPI

````yaml DELETE /v1/auth/sessions/{id}
openapi: 3.1.0
info:
  title: Recurso API
  version: 1.0.0
  description: |
    The Recurso billing engine REST API.

    Authenticate by passing your API key as a bearer token:

        Authorization: Bearer <api_key>

    Obtain an API key by registering a tenant via `POST /auth/register`.
    All authenticated endpoints live under the `/v1` prefix. Mutating
    endpoints support idempotency via the `Idempotency-Key` header.
  license:
    name: MIT
    identifier: MIT
servers:
  - url: https://billing.example.com
    description: >-
      Example deployment — substitute the base URL of your own Recurso
      deployment.
security:
  - bearerAuth: []
tags:
  - name: System
    description: Health, version, and API metadata
  - name: Auth
    description: Tenant registration
  - name: Plans
    description: Product catalog plans
  - name: Customers
    description: Customer management
  - name: Subscriptions
    description: Subscription lifecycle
  - name: Invoices
    description: Invoices, PDFs, and Indian GST e-invoicing
  - name: Coupons
    description: Discounts
  - name: Usage
    description: Metered usage events
  - name: Credit Notes
    description: Customer credits
  - name: Quotes
    description: Quote-to-invoice lifecycle
  - name: Webhooks
    description: Webhook endpoint management and event feed
  - name: Analytics
    description: Revenue analytics
  - name: Checkout
    description: Public hosted checkout for invoices
  - name: Payments
    description: Payment order creation
  - name: Inbound Webhooks
    description: Receivers for payment-gateway callbacks (Razorpay, Stripe)
  - name: Customer Portal
    description: Customer-facing portal — magic-link auth and session-scoped data
  - name: Developer
    description: API key management
  - name: Account
    description: Tenant account settings
  - name: Finance
    description: Ledger accounts, entries, reconciliation, and revenue recognition
  - name: Settings
    description: Tax (GST) and e-invoicing (IRP) configuration
  - name: Consents
    description: Consent records for RBI-compliant recurring billing
  - name: Referrals
    description: Customer referral program
  - name: Gifts
    description: Gift subscriptions
  - name: Mandates
    description: UPI Autopay mandates
  - name: Offline Payments
    description: Virtual accounts and manually recorded payments
  - name: Organizations
    description: Multi-entity organizations grouping several tenants
  - name: Accounting
    description: QuickBooks / Xero accounting integrations
  - name: Churn
    description: Churn risk scoring and alerts
  - name: Cancel Flows
    description: Configurable retention flows shown at cancellation time
  - name: Dunning
    description: Dunning analytics and multi-channel dunning campaigns
paths:
  /v1/auth/sessions/{id}:
    delete:
      tags:
        - Auth
      summary: Revoke a single session
      description: >
        Revokes one of the user's OWN sessions. A session that does not exist or
        belongs to another user returns 404 (no ownership leak).
      operationId: revokeSession
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Session revoked.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
      security:
        - sessionCookie: []
components:
  responses:
    Unauthorized:
      description: Missing or invalid credentials (API key or session cookie).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: The requested resource does not exist.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          description: Structured error detail.
          required:
            - code
            - message
          properties:
            code:
              type: string
              description: Stable machine-readable error code.
              examples:
                - validation_failed
                - unauthorized
                - forbidden
                - not_found
                - conflict
                - rate_limited
                - internal_error
                - invalid_api_key
                - key_mode_mismatch
                - over_refund
                - invoice_not_paid
                - invoice_already_paid
            message:
              type: string
              description: Human-readable explanation.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API key
      description: >-
        Tenant API key obtained from `POST /auth/register` or `POST
        /v1/developer/keys`.
    sessionCookie:
      type: apiKey
      in: cookie
      name: recurso_session
      description: >
        Dashboard user session cookie (httpOnly) issued by `POST /auth/register`
        and `POST /auth/login`. v1 endpoints accept EITHER this cookie or the
        tenant API key (`bearerAuth`).

````