Workspaces
Delete workspace
Delete a workspace and all its computers.
POST
Delete workspace
Deletes a workspace and every computer in it. Only the workspace owner can call this. An invited member gets
The request body is ignored.
403.
The verb is POST and the path ends in /delete. There is no DELETE handler on /workspaces/{id}. Sending DELETE there returns 405.
Order of operations
The endpoint is not a transaction. It runs these steps in this order:- Checks that you own the workspace. A member gets
403, and an unknown workspace gets404. - Deletes the workspace’s file records. This is permanent, and it happens before any computer is touched.
- Terminates each computer on its host, one at a time. A host that answers
404counts as already gone. A computer with no recorded host address is skipped. - Stops and returns
500if any termination failed. The workspace row and its computers stay in place. - Deletes the workspace row. The database cascade then removes the computer records.
Path parameters
string
required
Workspace ID. Required.
Response
boolean
true when the workspace and all of its computers were deleted. The endpoint never returns false. A failure comes back as a 4xx or 5xx instead.string
Human-readable confirmation. Currently
"Project deleted successfully".Example
Response
Errors
The scope check runs before the workspace lookup, so a workspace-scoped key targeting an ID that does not exist gets
403, not 404.