# Overview

## Schedules

Run an agent or a flow on a schedule: a cron expression in a timezone. Each occurrence is one fire, which starts one run as the schedule’s owner (re-checked at every fire), through the same path as `POST /v1/runs`; a run a schedule started names it (`Run.trigger`). After a gap, `catchUp` runs once for the latest missed occurrence (or skips them), never once per missed one; `overlap` skips an occurrence while the previous run is still going. `GET …/fires` is the schedule’s history; `run-now` fires it outside the schedule. Mounted when the deployment fires schedules.

## Operations

GET

[/v1/schedules](https://docs.kindgi.com/v0.1.10/reference/api/operations/scheduleslist.md)

POST

[/v1/schedules](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesregister.md)

GET

[/v1/schedules/{triggerId}](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesget.md)

PATCH

[/v1/schedules/{triggerId}](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesupdate.md)

POST

[/v1/schedules/{triggerId}/pause](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulespause.md)

POST

[/v1/schedules/{triggerId}/resume](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesresume.md)

POST

[/v1/schedules/{triggerId}/unregister](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesunregister.md)

GET

[/v1/schedules/{triggerId}/fires](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesfires.md)

POST

[/v1/schedules/{triggerId}/run-now](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulesrunnow.md)

POST

[/v1/schedules/{triggerId}/owner](https://docs.kindgi.com/v0.1.10/reference/api/operations/schedulestakeownership.md)