Skip to Content
SeyloDocs
API referenceBuilds

Change a service's build settings

POST
/api/v1/builds.updateSettings

Changes how a service is built. Omitted fields keep their value. Takes effect on the next deploy. buildNodeId must name a node with Can build on, or be null for automatic.

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}$
builder?string|string|string
contextPath?string
Match^(?!/)(?!.*(^|/)\.\.(/|$)).*$
Lengthlength <= 300
dockerfilePath?string
Match^(?!/)(?!.*(^|/)\.\.(/|$)).*$
Lengthlength <= 300
inlineDockerfile?|null
targetStage?string
Lengthlength <= 100
buildNodeId?|null
startCommand?string
Lengthlength <= 2000
installCommand?string
Lengthlength <= 2000
buildCommand?string
Lengthlength <= 2000

Response Body

Success.

application/json
  1. response
builder*string|string|string
contextPath*string
Match^(?!/)(?!.*(^|/)\.\.(/|$)).*$
Lengthlength <= 300
dockerfilePath*string
Match^(?!/)(?!.*(^|/)\.\.(/|$)).*$
Lengthlength <= 300
inlineDockerfile*|null
targetStage*string
Lengthlength <= 100
buildNodeId*|null
startCommand*string
Lengthlength <= 2000
installCommand*string
Lengthlength <= 2000
buildCommand*string
Lengthlength <= 2000
Example Request
curl -X POST 'https://example.com/api/v1/builds.updateSettings' \  -H 'Content-Type: application/json' \  -d '{  "serviceId": "string"}'
Example Response
{  "builder": "railpack",  "contextPath": "string",  "dockerfilePath": "string",  "inlineDockerfile": "string",  "targetStage": "string",  "buildNodeId": "string",  "startCommand": "string",  "installCommand": "string",  "buildCommand": "string"}

List the build queue GET

Lists builds that are queued or running on every node (or one node), oldest first, with their place in the queue. Only builds of services the caller can view are returned. Any signed-in caller. Available to MCP clients and the assistant.

Approve a CLI sign-in POST

Approves a pending CLI sign-in: the CLI gets an API key of yours, limited to the given actions ("*" for all of yours), optionally to some projects, read-only or not, expiring after expiresInDays (default 7, like the approval page). Browser sessions only, signed in or confirmed with auth.reauth in the last 15 minutes (FORBIDDEN details.reason "reauth" otherwise). Any signed-in caller. Not available to MCP clients or the assistant.