Check whether an app can use zero-downtime redeploys, and why not
Requires read scope and current ownership; another account's app is 404. Works for custom and catalog apps. Returns the same answer as impreza_get_zero_downtime and the My Apps card. eligible is true only when no reason applies. Each reason has a stable code, a scope, an English message and a remedy. App-scope reasons (catalog_app, preview, tor_egress, sandbox, no_proxy_route, compose_unreadable, multiple_services, container_name, network_mode, not_on_proxy_network, fixed_host_port, writable_volume) make POST /platform/deployments/custom/{id}/zero-downtime refuse the opt-in with 422 and the same reasons in error.details.reasons. Agent-scope reasons (agent_unknown, agent_unsupported) do not: the setting is saved and redeploys run normally until the agent supports ready-swap-v1 (agent 0.6.27 or newer). A Compose file that cannot be read is a reason, never eligible. Codes are only ever added.
Request
- Base URL: https://api.imprezahost.com/v1
- URL: https://api.imprezahost.com/v1/platform/deployments/{id}/zero-downtime
- Auth: API key in header X-API-Key and API key in header X-API-Secret
Response
Eligibility, every reason, the saved setting and the last outcome
Example response
{
"success": true,
"meta": {
"request_id": "req_a1b2c3d4e5f6g7h8",
"timestamp": "2026-03-30T14:05:00Z"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.