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, signed in or with a key for the whole account. An invited member gets
The request body is ignored.
403, described in Errors. A workspace key can’t delete a workspace, even its own, whatever its permissions.
The verb is POST and the path ends in /delete. DELETE /workspaces/{id} does the same, with the same answers.
Order of operations
The endpoint runs these steps in this order:- Checks that you own the workspace.
- Refuses with
409, before touching anything, when the workspace holds a device or dedicated machine that Orgo manages, has a dedicated computer purchase, has hourly or dedicated computer billing records, has an OpenClaw enrollment, or when another operation is already working on it. - Terminates each computer on its host, one at a time. A host that answers
404, or a computer with no recorded host address, does not stop the delete. A failed termination does not stop the loop either: every remaining computer is still tried. - Returns
500if any termination failed. The workspace, its file records, and the computers that were not terminated stay in place. - Deletes the workspace’s file records and the workspace row together. 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
A valid key that lacks access gets
403, as listed above. A server-side fault while verifying the credential answers 503 with Service temporarily unavailable. … as the message and Retry-After: 5. Retry that one.