Skip to content
LANrurugi

Signed-in Devices

3 endpoints.

List signed-in devices

Section titled “List signed-in devices”
GEThttp://localhost:3000/api/sessions

Every active refresh-token family — that is, every device currently signed in — including the one making this request, which is marked so a client does not offer to revoke itself by accident.

Requires a session-cookie login. An API token of either role is rejected.

Responses

200The active sessions.
[
  {
    "auto_name": "",
    "created_at": 0,
    "current": false,
    "custom_name": "",
    "expires_at": 0,
    "family_id": "",
    "idle_expires_at": 0,
    "ip": "",
    "last_seen_at": 0,
    "name": ""
  }
]

This endpoint accepts a browser session only — the cookie set when you log in to your own instance. API tokens are refused by the server, so there is no token field here and the command above carries no Authorization header.

Your own instance address. Requests go from this browser straight to it.

Revoke a signed-in device

Section titled “Revoke a signed-in device”
DELETEhttp://localhost:3000/api/sessions/{family_id}

Ends one session by revoking its whole refresh-token family, so the device must sign in again. Requires a session-cookie login.

Path parameters

family_idstringrequired

Responses

200Revoked.
{
  "error": "",
  "operation": "",
  "success": 0,
  "successMessage": ""
}
404No such session.
{
  "error": "",
  "operation": "",
  "success": 0,
  "successMessage": ""
}

This endpoint accepts a browser session only — the cookie set when you log in to your own instance. API tokens are refused by the server, so there is no token field here and the command above carries no Authorization header.

Your own instance address. Requests go from this browser straight to it.

Rename a signed-in device

Section titled “Rename a signed-in device”
PATCHhttp://localhost:3000/api/sessions/{family_id}

Sets a custom display name for one session, so a device list reads as “living room tablet” rather than as a user-agent string. Requires a session-cookie login.

Path parameters

family_idstringrequired

Request body

application/json

Responses

200Renamed.
{
  "error": "",
  "operation": "",
  "success": 0,
  "successMessage": ""
}
404No such session.
{
  "error": "",
  "operation": "",
  "success": 0,
  "successMessage": ""
}

This endpoint accepts a browser session only — the cookie set when you log in to your own instance. API tokens are refused by the server, so there is no token field here and the command above carries no Authorization header.

Your own instance address. Requests go from this browser straight to it.