Cron next
Exactcron_nextDeterministic and authoritative — the canonical answer for this input.
Enumerate the next N scheduled occurrences of a cron expression. Given an optional ISO 8601 from_datetime + IANA timezone, returns each occurrence as both local (tz-aware) and UTC ISO strings — DST handling is explicit in the output. Max count is 1000. Processing multiple inputs? Use `cron_next_batch` to do up to 1000 in one call.
Parameters
expressionstringrequiredcountintegeroptionalHow many future occurrences to return.
from_datetimestringoptionalISO 8601 datetime to start iteration from. If omitted, uses now in the specified timezone. Naive datetimes are interpreted in `tz`.
tzstringoptionalIANA timezone name, e.g. 'America/New_York'.
Call it
curl -X POST https://api.snipget.ai/v1/cron/next \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"expression":"0 9 * * 1-5","count":3,"from_datetime":"2026-04-13T10:00:00","tz":"UTC"}'The Batch tab sends up to 1000 inputs in one call via /v1/cron/next/batch.
Example response
{
"input": "0 9 * * 1-5",
"is_valid": true,
"tz": "UTC",
"from": "2026-04-13T10:00:00+00:00",
"count": 3,
"occurrences": [
{
"local": "2026-04-14T09:00:00+00:00",
"utc": "2026-04-14T09:00:00+00:00"
},
{
"local": "2026-04-15T09:00:00+00:00",
"utc": "2026-04-15T09:00:00+00:00"
},
{
"local": "2026-04-16T09:00:00+00:00",
"utc": "2026-04-16T09:00:00+00:00"
}
],
"dialect": "standard"
}FAQ
Why not just work out the next run dates myself?
AI models frequently hallucinate upcoming run times, especially around weekends and daylight-saving changes. This computes them deterministically from the real calendar, so the dates are the authoritative answer, not an estimate.
How does it handle timezones and daylight saving?
You pass an IANA timezone like 'America/New_York', and each occurrence comes back in both local time and UTC, so the daylight-saving handling is explicit and you can use whichever form you need.
How many runs can I get, and where do they start from?
Ask for up to 1000 with count, starting from now or from any from_datetime you provide. A naive datetime is read in the timezone you set; the example starts mid-Monday so the next weekday-9am run lands on Tuesday.
What does it NOT do?
It only calculates the times. It does not schedule, trigger, or run anything, and it does not describe the schedule in words (use Describe a cron expression for that).
What if my expression or timezone is wrong?
A bad expression or an unknown timezone returns is_valid false with a why_invalid reason (a billed data verdict). An out-of-range count (below 1 or above 1000) is a request mistake: rejected with an INVALID_INPUT error, not billed.