---
title: "Get a deployment's automatic backup schedule"
method: GET
path: "/backups/schedule/{id}"
tags: ["Platform"]
---

# Get a deployment's automatic backup schedule

`GET /backups/schedule/{id}`

## Request

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

Answers even when nothing has been configured: no stored row means
the DEFAULTS — daily, keeping 3 — not "off". `is_default` says which
of the two you are looking at.

`last_error`, `last_error_at` and `consecutive_failures` describe
scheduled runs that could not start (storage unreachable, TLS,
credentials): a short reason with credentials removed, when it
happened and how many runs in a row failed that way. They are
`null`, `null` and `0` once a run starts. A failed run also appears
in `GET /backups` as a failed job, and the retry waits 15 minutes,
doubling per consecutive failure up to 6 hours. A server whose agent
has not been in contact for two hours gets no new job: the round is
recorded the same way, and a queued job that never started is closed
as failed when its job token expires.

## Path parameters

- `id` string, required

## Response `200`

The schedule in force

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