Change a project's editor machine type, sandbox environment or idle shutdown
Changed onChanges the machine type, sandbox environment or idle shutdown of the project machine. A new idle shutdown applies right away; a stopped machine picks up the other changes on its next start. A running machine needs restart: true, otherwise the request returns 409 and changes nothing. If the restarted machine cannot start, the request returns 409 but keeps the change. A custom machine type only runs in its own sandbox environment, so moving off it needs a new type. To run a single detached run or session on another machine type, pass machineType when creating it.
Request
- Base URLhttps://api.deepnote.com/v2
- URLhttps://api.deepnote.com/v2/projects/{projectId}/machine
- AuthHTTP bearer
Path parameters
ID of the project whose machine to use.
Request body
Example request
{
"type": "fjord",
"idleShutdownSeconds": 3600,
"sandboxEnvironmentId": "deepnote"
}Response
Updated project machine
Example response
{
"machine": {
"status": "running",
"startingPhase": "pulling_image",
"type": {
"id": "fjord",
"name": "CPU (Plus)",
"type": "deepnote",
"vCpus": 4,
"memoryGiB": 16
},
"sandboxEnvironmentId": "deepnote",
"idleShutdownSeconds": 900
}
}Changes
- breaking
the response property
/became nullable for the status - breaking
the response property
/became nullable for the status - info
response property
machine/errorlist-of-types was narrowed by removing typesnullfrom media typeapplication/jsonof response200 - info
response property
machine/sandboxEnvironmentIdlist-of-types was narrowed by removing typesnullfrom media typeapplication/jsonof response200
- breaking
- info
added the required property
/to the response with the status
- info