---
title: "Get a deployment (catalog or custom)"
method: GET
path: "/platform/deployments/{id}"
tags: ["Platform"]
---

# Get a deployment (catalog or custom)

`GET /platform/deployments/{id}`

## Request

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

Application diagnostics (schema deployment-diagnostics-v1)
summarizes recorded runtime and latest-operation evidence with fixed findings and next actions.
Includes generated_at, runtime_state, runtime_observed_at, findings and not_checked.
Recovery warnings take priority. History causes match only the exact latest command.
is_live_check=false; automatic_actions=false. No HTTP, DNS, TLS or external-dependency probes.
See runtime-health.html#application-diagnostics for availability and limits.
last_operation.progress reports supported, step, label, reported_at, age_seconds, recovery and reason.
Agent 0.6.6+ reports the last step, not a live percentage. Saved final results are resent after restart
without re-execution. Agent 0.6.7+ may reconcile a completed preparation checkpoint (recovery=reconciling),
restore previous configuration and close the attempt without replay. Unconfirmed work, missing proof or replacement
uncertainty remains recovery=required and needs support. Wait for a terminal result before retrying.
Agent 0.6.8+ can wait for supervised pull/build completion (recovery=reconciling). Only a verified successful receipt permits preparation reconciliation; missing/invalid receipts, worker failure or timeout require review.
Agent 0.6.9+ also waits for the original supervised replacement (step=reconciling_replacement), including startup checks, hooks, routes and normal recovery. Its verified final outcome is delivered without repeating deployment. Missing proof still blocks the queue.
See the development status in the deployment progress guide before assuming availability.
See https://docs.imprezahost.com/deployment-progress.html.
Includes runtime (recent container observation) and last_operation
(latest deployment/update/rollback/restart/uninstall job). Agent 0.6.4+
observations expire after 120 seconds; agent silence over 90 seconds
yields unknown. Inspect runtime.reason and observed_at. Legacy status
and last_health_at are historical, not current availability. See
https://docs.imprezahost.com/runtime-health.html for states and scope.
Returns the deployment row. The same URL works for both catalog
and custom deployments — the server checks both tables and
responds with the matching shape.
Adds release_history with up to ten recent deploy and rollback attempts. Each entry
contains command_id, attempt_status, completed_at, release_id, rollback_supported,
rollback_status (restored, failed or null), rollback_release_id and
runtime_state_after_rollback (healthy or unknown). Recovery metadata
requires the updated agent; older results have null release fields.
A restored rollback does not change a failed attempt into success.
These are historical observations, not live availability guarantees.
Snapshot content, environment variables and image credentials are
never included in release_history.

## Path parameters

- `id` string, required

## Response `200`

Deployment found

## Other responses

- `401`: Invalid or missing API credentials
- `404`: Resource not found

---

[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)