---
title: "Queue the agent update job for one server"
method: POST
path: "/platform/servers/{agent_id}/agent-update"
tags: ["Platform"]
---

# Queue the agent update job for one server

`POST /platform/servers/{agent_id}/agent-update`

## Request

- Base URL: `https://api.imprezahost.com/v1`
- URL: `https://api.imprezahost.com/v1/platform/servers/{agent_id}/agent-update`
- Auth: API key in header `X-API-Key` and API key in header `X-API-Secret`

Explicit customer action. The control plane queues a single
agent_upgrade job over the existing polling channel; the agent
verifies the channel's signed release manifest (Ed25519, expiry,
sequence chain, artifact digests) before swapping its own binary,
keeps credentials, configuration and app containers untouched,
and restores the previous binary if startup fails. The job is
only reported as verified when the next heartbeat carries the
target version. Refused while any operation is pending on the
server, outside the maintenance window, when the agent is pinned,
already current, or does not announce agent-upgrade-v1.

## Path parameters

- `agent_id` string, required

## Response `202`

Update job queued

## Other responses

- `401`: Invalid or missing API credentials
- `404`: Resource not found
- `409`: Request would violate a unique constraint or state precondition

---

[API](https://skmtc.dev/imprezahost/apis/impreza-host-public-api.md) · [All operations](https://skmtc.dev/imprezahost/apis/impreza-host-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/imprezahost/apis/impreza-host-public-api/revisions/db86511f604f?raw)