---
title: "Check update readiness"
method: GET
path: "/api/stacks/{stackName}/update-readiness"
tags: ["Stacks"]
---

# Check update readiness

`GET /api/stacks/{stackName}/update-readiness`

Computes an advisory readiness verdict for updating the stack right
now, from the stored preflight result, open drift findings, live
container health, the pending image change, the rollback backup slot,
and node disk headroom. Advisory only: no verdict blocks an update.
Requires `stack:read` permission. Pass `service` to scope the verdict
to one Compose service on a multi-service stack.

## Path parameters

- `stackName` string, required

## Query parameters

- `service` string

## Headers

- `x-node-id` integer

## Response `200`

Readiness report.

- object
  - `stack` string, required
  - `computedAt` integer, required — Unix timestamp (ms) the report was computed.
  - `verdict` 'ready' | 'ready_with_warnings' | 'review_required' | 'blocked' | 'unknown', required
  - `signals` object[], required
    - `id` string, required
    - `status` 'ok' | 'warning' | 'attention' | 'blocked' | 'unknown', required
    - `title` string, required
    - `detail` string, required
    - `affectsVerdict` boolean, required

## Other responses

- `400` — Invalid service scope.
- `401` — Authentication required. Provide a valid Bearer token.
- `403` — Insufficient permissions or license tier.
- `500` — Internal server error.

---

[API](https://skmtc.net/studio-saelix/apis/sencho-api.md) · [All operations](https://skmtc.net/studio-saelix/apis/sencho-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/studio-saelix/sencho-api/versions/f36f82acae1d/schema)