MemorySync
API Reference · Control-plane API

Revoke Active Session

Revoke one other active session owned by the current user. Use /auth/logout for the bearer session making the request.

Endpoint contract

POST/auth/sessions/{session_id}/revoke
204 No Content

Use the exact method and path shown above. Paths are relative to the API base URL.

Authentication, permission, and scope

ControlRequired contract
AuthenticationBearer access token for the current user.
Permission or scopeCurrent authenticated session.
Resource scopeThe target session must belong to the caller and cannot be the current bearer session.

Request fields

FieldTypeContract
session_idinteger path parameterOwned session ID returned by GET /auth/sessions.
Request bodynoneNo body is accepted.

Code examples

import os
from memorysync import ControlPlaneClient


client = ControlPlaneClient(
    base_url="https://api.memorysync.io",
    access_token=os.environ["MEMORYSYNC_ACCESS_TOKEN"],
)


client.revoke_session(302)

Response shape

response.json
  • A successful response has status 204 and no body.
  • Attempting to revoke the current session through this route is rejected; use /auth/logout.

Status outcomes

HTTP outcomes
2xx
Request completed

Read the operation-specific response and persist only fields needed by the task.

400 / 422
Correct the request

Fix invalid path, query, or body fields before trying again.

401 / 403
Access denied

Refresh authentication or verify the required organization permission and scope.

404
Unavailable in scope

Treat the resource as unavailable without revealing whether it exists elsewhere.

429 / 5xx
Keep the action recoverable

Use returned retry metadata when present and reconcile uncertain mutations before repeating them.

Production handling

Production request path
  1. 01

    Authorize

    APP

    Confirm the signed-in principal may perform this product action.

  2. 02

    Validate

    INPUT

    Validate identifiers and body fields before sending the request.

  3. 03

    Call

    SDK

    Use the named ControlPlaneClient method or equivalent HTTPS request from a trusted application context.

  4. 04

    Inspect

    RESULT

    Remove the confirmed session from local state after 204.

  5. 05

    Reconcile

    SAFE

    If the result is uncertain, list active sessions before sending another revoke.

Security notes

Control-plane safety

Required

Keep organization controls inside trusted boundaries.

  • Only present session IDs returned for the current user.
  • Require user confirmation for remote sign-out.
  • Do not reveal whether an unowned session ID exists.

Avoid

Do not weaken the route contract in client code.

  • Do not expose bearer or refresh tokens in URLs, logs, or public clients.
  • Do not accept organization, member, project, or resource IDs without application authorization.
  • Do not treat returned data as trusted HTML, prompt instructions, or proof of application authorization.

Related reference

List Active Sessions

Find another active session ID.

Account Authentication

Use logout for the current session.

Authentication

Compare bearer-authenticated control-plane clients with the memory API-key client.

API Overview

Choose the SDK client and authentication contract for the operation.

Was this page helpful?
← Previous
List Active Sessions
Next →
Create Organization