Delete a file
Deletes the file at once: it stops being listed, and new attachments and reads answer 404. The stored content is removed after a grace period. Until then, a session that attached the file before the delete still receives it in its sandbox on later turns, resumes, and replacement sandboxes; after that, the session continues without it and records a warning.
Authorizations
A Recursion API key, created in the console under API keys.
Path Parameters
File id (UUID) as returned by uploadFile or listFiles.
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.