Skip to main content
DELETE
Delete Artifact
Moves an artifact to the trash. It stays there for 30 days, and anyone who could delete it can bring it back with Restore until its purgeAt. Then it is removed for good, with every version. For a standalone artifact only the owner can delete it — team members cannot delete each other’s work. For an artifact in a workspace, you need deleteContent (editors and admins). MCP: artifact_delete. CLI: rip artifact delete <id>. Auth: Authorization: Bearer tr_...

Path parameters

Request body

JSON. A query parameter is refused (400 INVALID_FIELD).

Response

200 with the trash dates:
Deleting an artifact that is already in the trash returns its original dates. A workspace delete advances the artifact’s workspaceRevision and records artifact.deleted in the workspace change feed.

While it is in the trash

  • It leaves listings and search, and its alias stays held (ALIAS_CONFLICT names the purge date).
  • Reads by ID or alias, and writes, answer 410 DELETED with type, id, deletedAt and purgeAt. A caller who may restore it also gets restorable, deletedBy and, for a workspace artifact, workspaceId and workspaceRevision. Anyone who could not read it gets their usual refusal.
  • After purgeAt the artifact can no longer be restored, and the daily purge removes it. Its URL then answers 404.

Errors

To remove it for good before its purge date, use Purge from Trash (MCP trash_purge, CLI rip trash purge); it cannot be undone. Deleting one version (Delete Version) or table rows is immediate and permanent.