Soft delete a session subtree (events retained)
Soft deletes the session subtree: it is stopped if still running, sandbox teardown is requested, and its rows disappear from reads. A pending hard-stop sandbox cleanup returns retryable 409 conflict; retry after cleanup finishes, and seek operator attention if it remains pending. The transcript is retained, so this is not a data-erasure operation and cannot be undone through this API.
Authorizations
A Recursion API key, created in the console under API keys.
Headers
Optional tenant consistency check. When present, it must name the tenant bound to the API key, including when x-organization-id is default.
1Organization in which to act. Required for a tenant-scoped API key. Optional for an organization-scoped key, where it must name that same organization. The value may be an organization id or default.
1Path Parameters
Session id (UUID) as returned by managedAgentsStartSession or managedAgentsListSessions.
Response
Shared response body of every soft-delete endpoint, on agents, environments, tags, vaults, vault credentials, webhook bindings, and sessions. Soft delete is a tombstone, not an erase: the row stops appearing in list and get responses but is retained, and there is no undelete endpoint to bring it back. Irreversible erasure is the separate, confirmation-gated purge path.
Shared response body of every soft-delete endpoint, on agents, environments, tags, vaults, vault credentials, webhook bindings, and sessions. Soft delete is a tombstone, not an erase: the row stops appearing in list and get responses but is retained, and there is no undelete endpoint to bring it back. Irreversible erasure is the separate, confirmation-gated purge path.
Always true. The record was soft deleted and is now excluded from reads; a delete that did not happen is an HTTP error instead, so this field never reports false.