---
title: "Restore a deleted schedule"
method: POST
path: "/v1/schedules/{id}/restore"
tags: ["schedules"]
---

# Restore a deleted schedule

`POST /v1/schedules/{id}/restore`

## Request

- Base URL: `https://api.brixsignage.com`
- URL: `https://api.brixsignage.com/v1/schedules/{id}/restore`
- Auth: HTTP bearer

Restore a deleted schedule so its block layout returns to the schedule library.

**Notes.**
- Also restores the cross-workspace shares that were removed when the schedule was deleted.

## Path parameters

- `id` string, required

## Response `200`

Success.

- object
  - `data` object, required
    - `id` string, required
    - `restored` true, required

## Other responses

- `401`: Missing, expired or revoked bearer token.
- `403`: The token lacks the permission this operation needs (see `x-brix-permission`).
- `404`: No such schedule in this workspace.
- `409`: `not_deleted`: the schedule is not in the recycle bin.
- `5XX`: Server error. The body carries a `requestId` to quote to support.

---

[API](https://skmtc.dev/brixsignage/apis/brix-api.md) · [All operations](https://skmtc.dev/brixsignage/apis/brix-api/llms.txt) · [OpenAPI document](https://skmtc.dev/brixsignage/apis/brix-api/revisions/02fd3665dc7d?raw)