Skip to Content
SeyloDocs
API referenceServices

Set replicas per node

POST
/api/v1/services.setPlacements

Sets on which nodes a service runs and how many replicas on each. Several nodes are load balanced through each node's edge. Services with volumes run on one node only (use services.move to change it). Deploys the change right away.

Needs services.scale 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}$
placements*array<>
Items1 <= items <= 64
stickySessions?boolean
entryNodeId?|null

Response Body

Success.

application/json
  1. response
placements*array<>
stickySessions*boolean
entryNodeId*|null
Example Request
curl -X POST 'https://example.com/api/v1/services.setPlacements' \  -H 'Content-Type: application/json' \  -d '{  "serviceId": "string",  "placements": [    {      "nodeId": "string",      "replicas": 1    }  ]}'
Example Response
{  "placements": [    {      "nodeId": "string",      "nodeName": "string",      "replicas": 1    }  ],  "stickySessions": true,  "entryNodeId": "string"}

Edit a service's notes POST

Replaces the free-text notes of a service (Markdown, shown on its Notes tab). Notes are not secret; keep secrets in the environment. Needs `services.update` on the service (a grant on its project covers it). Available to MCP clients and the assistant.

Set a service's resource limits POST

Sets memory limit and reservation, CPU weight and process limit. Every field is off (null) by default; there is no hard CPU cap. Applies on the next deploy. Needs `services.update` on the service (a grant on its project covers it). Available to MCP clients and the assistant.