Skip to Content
SeyloDocs
API referenceServices

Edit a service's notes

POST
/api/v1/services.setNotes

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.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
serviceId*string

Panel-issued id.

Match^[a-z0-9]{16}$
notes*string
Lengthlength <= 20000

Response Body

Success.

application/json
  1. response
notes*string
updatedAt*string
Formatdate-time
Example Request
curl -X POST 'https://example.com/api/v1/services.setNotes' \  -H 'Content-Type: application/json' \  -d '{  "serviceId": "string",  "notes": "string"}'
Example Response
{  "notes": "string",  "updatedAt": "2019-08-24T14:15:22Z"}

Set a service's health check and deploy strategy POST

Sets the custom health check (null = TCP on the first port) and how deploys roll out: rolling (zero downtime, health gated) or recreate, and how long a new version may take to become healthy. 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.

Set replicas per node POST

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.