Skip to Content
SeyloDocs
API referenceServices

Move a service to another node

POST
/api/v1/services.move

Moves a single-node service to another node: deploys it there, copies its volumes while the old copy is stopped, switches traffic, then removes the old copy. Progress shows as a deployment with trigger move; on failure the service stays on the old node.

Needs services.move on the service (a grant on its project covers it). Available to MCP clients and the assistant.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
serviceId*string

Panel-issued id.

Match^[a-z0-9]{16}$
toNodeId*string

Panel-issued id.

Match^[a-z0-9]{16}$

Response Body

Success.

application/json
  1. response
deploymentId*string

Panel-issued id.

Match^[a-z0-9]{16}$
Example Request
curl -X POST 'https://example.com/api/v1/services.move' \  -H 'Content-Type: application/json' \  -d '{  "serviceId": "string",  "toNodeId": "string"}'
Example Response
{  "deploymentId": "string"}

List a project's services GET

Lists the services of a project with their kind, live status, source line, address, nodes, current CPU and memory, and live version. Compose members follow their stack. Needs `services.view` on the project. Available to MCP clients and the assistant.

Restart a service POST

Restarts the running containers of a service without deploying: same version, same settings. Use deployments.deploy to apply changed settings. Needs `services.control` on the service (a grant on its project covers it). Available to MCP clients and the assistant.