Update a sandbox's timeouts

Change a running Runpod sandbox’s idle timeout. The new idle deadline is recalculated from the sandbox’s last recorded activity, not from now.

PATCH /v2/sandboxes/{id}

cURL

curl --request PATCH \
  --url https://api.runpod.io/v2/sandboxes/SANDBOX_ID \
  --header "Authorization: Bearer $RUNPOD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"idleTimeoutSeconds": 1800}'

200

{
  "id": "7h3sbx91kq",
  "state": "RUNNING",
  "idleTimeoutSeconds": 1800,
  "lastActivityAt": "2026-10-19T14:02:40Z",
  "idleExpiresAt": "2026-10-19T14:32:40Z",
  "...": "..."
}

Changes the idle timeout of a running sandbox. The new idleExpiresAt is calculated from the sandbox’s lastActivityAt, not from the time of the request.

Values above your account’s maximum are clamped to it, and values under 90 seconds are raised to 90. Read the response for the value applied.

To change the maximum lifetime, use Extend a sandbox’s lifetime.

Review question: Is idleTimeoutSeconds the only field PATCH accepts, or can it also change other settings? Remove this box before merging.

Path parameters

id · string · required

The sandbox ID.

Body

idleTimeoutSeconds · integer

New idle timeout in seconds.

Response

Returns the updated sandbox. See Get a sandbox for all fields.

Errors

Status	Meaning
400	The request is malformed.
401	The API key is missing or invalid.
403	The API key doesn’t have access to sandboxes.
404	No sandbox with this ID exists on your account.
422	The request can’t be applied, for example the sandbox is no longer running.
429	Too many requests. Retry after a delay.

cURL

curl --request PATCH \
  --url https://api.runpod.io/v2/sandboxes/SANDBOX_ID \
  --header "Authorization: Bearer $RUNPOD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"idleTimeoutSeconds": 1800}'

200

{
  "id": "7h3sbx91kq",
  "state": "RUNNING",
  "idleTimeoutSeconds": 1800,
  "lastActivityAt": "2026-10-19T14:02:40Z",
  "idleExpiresAt": "2026-10-19T14:32:40Z",
  "...": "..."
}