Skip to main content
POST
Stop computer
Stops a running computer. Its disk is archived to object storage, so files, installed software, and configuration are all kept. Its host and IP are released, so a stopped computer costs no compute. A successful stop leaves the computer in status frozen. That is the value GET /computers/{id} reports afterwards, and the state start restores from.
The archive is written and verified before the computer is torn down. If the response is lost or finalization fails, check the operation status: needs_review means the result must be reconciled before retrying. A stopped computer has no instance_id until it is started again, so address it by UUID. On start it gets a new instance_id and can land on a different host with a different address and ports. Processes and other in-memory state are not preserved. Only the disk survives.

Path parameters

string
required
Computer UUID or instance_id. Both resolve to the same computer.

Query parameters

string
default:"false"
true or false. true returns 202 immediately instead of waiting, as described in Return immediately and poll. Any other value returns 400.

Response

boolean
true when the computer was stopped, or was already frozen.
Stopping is idempotent only for a computer that is already frozen. Any other non-running status returns 409 rather than succeeding. That includes stopped, which Orgo records when a computer’s virtual machine has stopped or is gone from its host. Only Linux and Windows computers can be stopped. Any other operating system, or a physical device, returns 400 with code STOP_UNSUPPORTED.

Example

Response

Errors

A failure that happens while the operation runs also carries operation_id and poll_url in its body. A host that refuses the archive answers with its own 4xx status and code.

Return immediately and poll

Send ?async=true, a JSON body { "async": true }, or the header Prefer: respond-async to return 202 immediately. The response includes id (the computer UUID), status (starting or stopping), operation_id, operation, and poll_url, plus Location and Retry-After: 2 headers. Repeating the same action while it is pending returns the same operation. An opposite action returns 409 with code OPERATION_IN_PROGRESS. Fetch poll_url with the same authentication until the operation reports succeeded, failed, or needs_review. A needs_review result means the host’s outcome is uncertain. Orgo checks the computer and settles the operation on its own; until then, a new start or stop returns 409 with code OPERATION_NEEDS_REVIEW. See Get computer operation. Without the async option the request waits for completion, up to 300 seconds. If still pending, it returns 202 and the same polling fields. Both modes preserve disk data; stopping discards live processes and memory, and starting cold-boots with potentially different connection details.

Authorizations

Authorization
string
header
required

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

Headers

Prefer
enum<string>

Send respond-async for the same effect as ?async=true.

Available options:
respond-async

Path Parameters

id
string
required

Computer ID

Query Parameters

async
enum<string>
default:false

true returns 202 immediately instead of waiting. Omitted, the request waits up to 300 seconds. Any value other than true or false returns 400.

Available options:
true,
false

Body

application/json
async
boolean
default:false

true returns 202 immediately. An empty body is accepted; any body that is not a JSON object with an optional boolean async returns 400.

Response

Stopped, or already frozen

success
boolean
Example:

true