Schedules

The schedule format a job accepts, and the call that shows when a schedule runs next.

Schedule format

A schedule is 5 fields separated by spaces, or one of the shortcuts below.

Field	Values	Names
Minute	`0` to `59`
Hour	`0` to `23`
Day of month	`1` to `31`
Month	`1` to `12`	`JAN` to `DEC`
Day of week	`0` to `7`, where `0` and `7` are Sunday	`SUN` to `SAT`

Each field takes:

Form	Example	Means
`*`	`*`	Every value
A value	`5`	That value
A range	`1-5`	Every value from the first to the last
A list	`1,15`	Each value listed
A step	`*/15` or `0-30/10`	Every nth value, over all values or over a range

Shortcut	Same as
`@hourly`	`0 * * * *`
`@daily`	`0 0 * * *`
`@weekly`	`0 0 * * 0`
`@monthly`	`0 0 1 * *`
`@yearly`	`0 0 1 1 *`

Time zone

A timeZone is an IANA time zone name, such as Africa/Dar_es_Salaam, Africa/Nairobi, or UTC. When it is empty, the schedule runs in UTC. See When clocks change.

Preview a schedule

POST/v1/schedules/preview

Returns the next 5 times a schedule runs, without creating a job. A schedule or time zone we cannot read gets Validation failed.

Request

schedulestringRequired: The schedule to check.
timeZonestring: The time zone to run it in. UTC when empty.

Response

{
  "data": {
    "schedule": "30 8 * * MON-FRI",
    "timeZone": "Africa/Dar_es_Salaam",
    "next": [
      "2026-09-28T05:30:00Z",
      "2026-09-29T05:30:00Z",
      "2026-09-30T05:30:00Z",
      "2026-10-01T05:30:00Z",
      "2026-10-02T05:30:00Z"
    ]
  },
  "meta": { "requestId": "01m3c081dbf3j55x7hsa7wc1yj" }
}

The times in next are in UTC.

Last updated 26 September 2026