---
title: "Resume a paused computer, optionally for a set number of hours"
method: POST
path: "/api/computers/{id}/resume"
tags: ["computers"]
---

# Resume a paused computer, optionally for a set number of hours

`POST /api/computers/{id}/resume`

## Request

- Base URL: `https://www.orgo.ai`
- URL: `https://www.orgo.ai/api/computers/{id}/resume`
- Auth: HTTP bearer

Brings a suspended computer back with its memory. Body, optional: ends_in_hours or ends_at, and on_end, as on Start (the computer is deleted when the end is up): checked before anything resumes, set once it is running (an hourly computer prepays to it), and the 200 carries ends_at, on_end (read only), deletes_at and the prepay. A resume still under way (202: its memory is coming back from storage) sets no end and says end_not_set with code STILL_RESUMING; set it with PATCH once it is running. An end that could not be set never fails the resume: the 200 carries end_not_set.

## Path parameters

- `id` string, required

## Request body

- object
  - `ends_in_hours` integer, nullable
  - `ends_at` string, date-time, nullable
  - `on_end` 'delete' | 'null', nullable: Not a choice: a computer with an end is deleted when its time is up, running or not, with everything on it. "delete" is accepted and changes nothing; omitted or null is the same. Any other value, "stop" included, is 400 INVALID_ENDS: "A computer with an end is deleted when its time is up. To keep a computer, leave out the end." On a computer (GET, the listing, and the create, PATCH, Start and Resume answers) on_end is read only: "delete", "stop" for a computer whose end was set before this rule (stopped then, and deleted 7 days later unless it is started), or null with no end.

## Response `200`

Running: success and status running, with the end as on Start.

## Other responses

- `202`: Still resuming (status resuming, or waking for a computer asleep in storage); with an end asked for, end_not_set STILL_RESUMING.
- `400`: INVALID_ENDS (as on Start, an on_end other than "delete" or one without ends_in_hours or ends_at among them) or ENDS_NOT_SUPPORTED. Nothing resumed.
- `403`: View only access (workspace_read_only), or an end asked for by a caller PATCH refuses (computer_key, computer_scope), as on Start. Nothing resumed.
- `409`: Not suspended, or its memory is still being saved (suspend_in_progress).
- `429`: Over one of the account's rate limits (rate_limited): `limit` names it, `retry_after` and Retry-After say how many seconds to wait. Limits are per account (the workspace owner when the request acts on a computer or a workspace) and set by its plan (x-rate-limits).
- `503`: ENDS_UNAVAILABLE, or its memory cannot be reached right now.

## Changes

- **2026-10-30** `afb6f0ee1aac`: 2 info
  - added the new optional request property `on_end`
  - added the non-success response with the status `429`
- **2026-10-28** `354a2c3d47fc`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/orgo/apis/orgo-api/changes/api/computers/:id/resume/post.md)

---

[API](https://skmtc.dev/orgo/apis/orgo-api.md) - [All operations](https://skmtc.dev/orgo/apis/orgo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/orgo/apis/orgo-api/revisions/e4c1e7379fa5?raw)