Skip to main content
POST
Delete workspace
Deletes a workspace and every computer in it. Only the workspace owner can call this. An invited member gets 401 or 403, described in Errors. The verb is POST and the path ends in /delete. There is no DELETE handler on /workspaces/{id}. Sending DELETE there returns 405.
This cannot be undone. Every computer in the workspace is terminated and its disk destroyed.

Order of operations

The endpoint runs these steps in this order:
  1. Checks that you own the workspace.
  2. 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.
  3. 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.
  4. Returns 500 if any termination failed. The workspace, its file records, and the computers that were not terminated stay in place.
  5. Deletes the workspace’s file records and the workspace row together. The database cascade then removes the computer records.
A 500 does not mean the workspace is intact. Every computer whose termination succeeded is already destroyed, including any after the one that failed. A retry does not re-send the failed terminations. It returns 409 with teardown_reconciliation_required until Orgo support confirms what happened to them. Contact support to finish the delete.

Path parameters

string
required
Workspace ID. Required.
The request body is ignored.

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

This endpoint answers every failed authorization check with 401, including a valid key that lacks access. A server-side fault while verifying the credential also comes back as 401, with Service temporarily unavailable. … as the message. Retry that one.

Authorizations

Authorization
string
header
required

API key authentication. Get your key at orgo.ai/workspaces

Path Parameters

id
string
required

Workspace ID

Response

Workspace deleted

success
boolean
Example:

true

message
string

Human-readable confirmation.

Example:

"Project deleted successfully"