Skip to the page

Start a stopped environment from its kept data

POST/v1/organisations/{id}/environments/{envId}/restore

Operation environments.restore · since 2026-11-05 · stable

Needs a session withwritescopeAnswers200 OK

{ "ok": true } once the restore is asked for. The environment's operation then runs on its own: follow it with environments.get or rykloud envs watch.

Path parameters

idstring (uuid)required
The organisation id.
envIdstring (uuid)required
The environment id.

Body

None. Send no body, or an empty JSON object.

Errors

Every error is { "error", "message", "detail"? } (Errors and references). Besides the codes any route can answer, this one refuses with:

  • wrong_state
  • busy
  • suspended
  • limit_spend
POST/v1/organisations/{id}/environments/{envId}/restore
curl -X POST "https://api.rykloud.com/v1/organisations/$ORG_ID/environments/$ENV_ID/restore" \
  -H "Authorization: Bearer $RYKLOUD_TOKEN"
With the rykloud CLI
rykloud envs restore [ENV] [flags]

Command reference: rykloud envs restore