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

# Restore a recalled schedule

`POST /v1/recall/schedule/{id}/restore`

## Request

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

Put a recalled schedule back on the screens it was removed from. Nothing was changed by the recall, so playback resumes exactly as it was before.

## Path parameters

- `id` string, required

## Response `200`

Success.

- object
  - `data` object, required
    - `id` string, required
    - `kind` 'media' | 'creative' | 'playlist' | 'schedule', required
    - `recalledAt` unknown, required

## Other responses

- `401`: Missing, expired or revoked bearer token.
- `403`: You do not hold `schedule.edit` where the schedule lives.
- `404`: No such schedule in this workspace.
- `409`: `not_recalled`: it is not recalled.
- `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)