Skip to Content
SeyloDocs
API referenceServices

Stop a service

POST
/api/v1/services.stop

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.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
serviceId*string

Panel-issued id.

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

Response Body

Success.

application/json
  1. response
Example Request
curl -X POST 'https://example.com/api/v1/services.stop' \  -H 'Content-Type: application/json' \  -d '{  "serviceId": "string"}'
Example Response
{}

Start a stopped service POST

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.

Change a service's general settings POST

Renames a service or changes its container settings, ports or cron schedule. Omitted fields keep their value. Changes to what runs apply on the next deploy; a rename updates the network alias on the next deploy too. Needs `services.update` on the service (a grant on its project covers it). Available to MCP clients and the assistant.