Skip to Content
SeyloDocs
API referenceDocker cleanup

Clean up a node

POST
/api/v1/cleanup.run

Removes unused images, build cache, stopped containers and (when asked) orphaned service data created by this panel on one node. Never touches anything else on the machine.

Needs nodes.manage, which owners and admins hold. Available to MCP clients and the assistant, after a person approves the call.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
nodeId*string

Panel-issued id.

Match^[a-z0-9]{16}$
images?boolean
Defaulttrue
buildCache?boolean
Defaulttrue
stoppedContainers?boolean
Defaulttrue
orphanedServiceData?boolean
Defaultfalse

Response Body

Success.

application/json
  1. response
nodeId*string

Panel-issued id.

Match^[a-z0-9]{16}$
bytes*integer
Range0 <= value
items*array<string>
Example Request
curl -X POST 'https://example.com/api/v1/cleanup.run' \  -H 'Content-Type: application/json' \  -d '{  "nodeId": "string"}'
Example Response
{  "nodeId": "string",  "bytes": 0,  "items": [    "string"  ]}

Preview a cleanup GET

Lists what a cleanup of this node would remove and how much space it frees, without removing anything. Needs `nodes.manage`, which owners and admins hold. Available to MCP clients and the assistant.

Add a custom domain POST

Adds a custom domain (and optional path) to a service and returns it together with the DNS record to create. The route goes live once DNS points at the service's node and a certificate is issued. Set forward to make it a redirect-only domain, for example www to the apex. Needs `domains.edit` on the service (a grant on its project covers it). Available to MCP clients and the assistant.