Skip to main content
POST
Delete session

Restrictions

Usage

  • Requires manage rights on the session: a personal session (team_id = 0) can be deleted only by its creator; a team session by its creator or a member of the owning team. Account owners and admins get no exemption; anyone else receives AccessDenied.
  • An unknown or already-deleted session_id returns ResourceNotFound.
  • Background processes the session still runs (background shell commands, monitors) are stopped first on a best-effort basis; a failed stop does not block the delete.
  • Child subagent sessions and the files the session presented are deleted in the same transaction; the stored file contents are removed afterwards on a best-effort basis.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Session deletion by ID.

session_id
string
required

Target session ID, from the list returned by POST /safari/session/list.

Minimum string length: 1

Response

Success

Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

error
object

Error payload inside the response envelope. Present only on non-2xx responses.

data
null

Not returned on success; the body carries only request_id.