Skip to content
Docs

Force restart a project daemon instance

POST/__remote/api.vercel.com/v1/projects/{idOrName}/daemons/{daemonName}/instances/{instanceId}/restart
Force restart a running production daemon instance. The new container starts asynchronously after the restart is accepted.
/__remote/api.vercel.com/v1/projects/{idOrName}/daemons/{daemonName}/instances/{instanceId}/restart
const response = await fetch('/__remote/api.vercel.com/v1/projects/idOrName/daemons/daemonName/instances/instanceId/restart?teamId=string&slug=string', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
    'Content-Type': 'application/json',
  },
});


const data = await response.json();
console.log(data);
Response
{
  "ok": "false"
}

Authentication

AuthorizationbearerToken

Default authentication mechanism

Path parameters

idOrNamestringRequired
The unique project identifier or the project name
daemonNamestringRequired
The name of the daemon that owns the instance
instanceIdstringRequired
The ID of the daemon instance to restart

Query parameters

teamIdstringOptional
The Team identifier to perform the request on behalf of.
slugstringOptional
The Team slug to perform the request on behalf of.

Response

202The restart was accepted. The new user container starts asynchronously.
okbooleanRequired

Errors

400One of the provided values in the request query is invalid.
401The request is not authorized.
403You do not have permission to access this resource. The OIDC token is not a production token for this project.
404The daemon has no running production instance with this ID.
409The instance is still starting and cannot be restarted yet.
410Error
500The instance controller did not accept the restart.