Skip to Content
SeyloDocs
API referenceUpdates

List past updates

GET
/api/v1/updates.history

Lists update runs (panel, agents and Docker), newest first, with each step's outcome.

Needs nodes.view, which owners and admins hold. Available to MCP clients and the assistant.

Authorization

cookieseylo_session<token>

Query Parameters

limit?integer
Range1 <= value <= 100
Default20
before?string
Formatdate-time

Response Body

Success.

application/json
  1. response
runs*array<>
hasMore*boolean
Example Request
curl -X GET 'https://example.com/api/v1/updates.history'
Example Response
{  "runs": [    {      "id": "string",      "targetVersion": "string",      "trigger": "auto",      "status": "running",      "startedBy": "string",      "error": "string",      "createdAt": "2019-08-24T14:15:22Z",      "finishedAt": "2019-08-24T14:15:22Z",      "doneSteps": 0,      "totalSteps": 0,      "steps": [        {          "id": "string",          "position": 0,          "target": "panel",          "nodeId": "string",          "nodeName": "string",          "fromVersion": "string",          "toVersion": "string",          "status": "pending",          "error": "string",          "startedAt": "2019-08-24T14:15:22Z",          "finishedAt": "2019-08-24T14:15:22Z"        }      ]    }  ],  "hasMore": true}

Check for updates now POST

Fetches and verifies the signed release manifest now instead of waiting for the next scheduled check. Needs `updates.manage`, which owners and admins hold. Available to MCP clients and the assistant.

Turn auto-update on or off POST

Turns automatic updates of the panel and all nodes on or off. When on, new releases roll out panel first, then node by node. Needs `updates.manage`, which owners and admins hold. Available to MCP clients and the assistant.