List the build queue
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.
seylo_session<token>nodeId?stringPanel-issued id.
^[a-z0-9]{16}$Success.
application/json- response
builds*array<>curl -X GET 'https://example.com/api/v1/builds.queue'{ "builds": [ { "id": "string", "deploymentId": "string", "serviceId": "string", "serviceName": "string", "projectId": "string", "projectName": "string", "nodeId": "string", "nodeName": "string", "builder": "railpack", "status": "queued", "position": 1, "commitSha": "string", "queuedAt": "2019-08-24T14:15:22Z", "startedAt": "2019-08-24T14:15:22Z" } ]}Get a service's build settings GET
Returns how a service is built (builder, paths, inline Dockerfile, command overrides, build node) and the nodes it could build on, with whether each can build. Needs `services.view` on the service (a grant on its project covers it). Available to MCP clients and the assistant.
Change a service's build settings POST
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.