Start a stopped service
Starts a stopped service with its live version on its nodes. Does not deploy new code.
Needs services.control on the service (a grant on its project covers it). Available to MCP clients and the assistant.
seylo_session<token>application/json- body
serviceId*stringPanel-issued id.
^[a-z0-9]{16}$Success.
application/json- response
curl -X POST 'https://example.com/api/v1/services.start' \ -H 'Content-Type: application/json' \ -d '{ "serviceId": "string"}'{}Set a service's volumes POST
Replaces a service's named volumes (persistent folders mounted into the container). Volumes are matched by name: new names are created, missing ones are removed with their data. Applies on the next deploy. Services with volumes run on one node. Needs `services.update` on the service (a grant on its project covers it). Available to MCP clients and the assistant, after a person approves the call.
Stop a service POST
Stops every replica of a service. Volumes, domains (which show the status page) and history stay; start brings it back. Needs `services.control` on the service (a grant on its project covers it). Available to MCP clients and the assistant.