MemorySync
API Reference · Control-plane API

List Active Sessions

List the current user’s active sessions through the safe self-service endpoint without exposing refresh-token hashes or device fingerprints.

Endpoint contract

GET/auth/sessions
200 OK

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 scopeOnly active, non-expired sessions owned by the caller are returned.

Request fields

FieldTypeContract
Request bodynoneThis endpoint accepts no request body.

Code examples

import os
from memorysync import ControlPlaneClient


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


sessions = client.list_sessions()

Response shape

response.json
{"sessions":[{"id":301,"is_current":true,"session_type":"browser","session_name":"Chrome on Windows","user_agent":"Mozilla/5.0","ip":"203.0.113.10","location":"Example City","geo":null,"created_at":"2026-07-31T09:00:00Z","last_activity_at":"2026-08-01T11:55:00Z","expires_at":"2026-08-08T09:00:00Z"}],"current_session_id":301}
  • The response intentionally omits refresh-token hashes, token-family details, and device fingerprints.
  • Use is_current to prevent the wrong revoke action in your UI.

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

    Render active sessions and clearly mark the current one.

  5. 05

    Reconcile

    SAFE

    Refresh the list after a revoke or logout-all operation.

Security notes

Control-plane safety

Required

Keep organization controls inside trusted boundaries.

  • Do not use IP or user-agent strings as proof of identity.
  • Safely encode session names and location fields.
  • Keep bearer tokens out of client-visible logs.

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

Revoke Session

Revoke another owned session.

Account Authentication

Review login and logout endpoints.

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
Test API Key
Next →
Revoke Active Session