---
title: "Restore schedule"
method: POST
path: "/api/v1/schedules/{scheduleId}/restore"
tags: ["Schedules"]
---

# Restore schedule

`POST /api/v1/schedules/{scheduleId}/restore`

## Request

- Base URL: `https://omniapp.co` (the document declares no server; this is the origin it was published from)
- URL: `https://omniapp.co/api/v1/schedules/{scheduleId}/restore`
- Auth: HTTP bearer

Take a schedule out of the trash. It runs on its schedule again unless it was paused or disabled by the system. A schedule whose document is in the trash cannot be restored.

## Path parameters

- `scheduleId` string, uuid, required: The UUID of the scheduled task. Can be found in the schedule's URL after /schedules/.

## Response `200`

Schedule restored, or it was not in the trash and is left as it was

- SuccessResponse
  - `success` boolean, required: Whether the operation was successful

## Other responses

- `401`: Authentication required
- `403`: Permission denied - must be schedule owner or have manage permission. Also returned, whether or not the schedule is in the trash, when it delivers to a destination type the organization has turned off or its owner is no longer in the organization.
- `404`: Schedule not found, or its document is in the trash

## Changes

- **2026-10-29** `6c4d29f19093`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/omniapp/apis/omni-api/changes/api/v1/schedules/:scheduleId/restore/post.md)

---

[API](https://skmtc.dev/omniapp/apis/omni-api.md) - [All operations](https://skmtc.dev/omniapp/apis/omni-api/llms.txt) - [OpenAPI document](https://skmtc.dev/omniapp/apis/omni-api/revisions/76b40ebc2292?raw)