Time - Scheduling

Free Cron API Endpoint

The free cron API endpoint takes a five-field cron expression and answers the next times it fires, in the time zone you name, as Unix timestamps and ISO 8601. It calculates and nothing more: no job is stored and no URL is called. For a URL called on a schedule, use Webhook Schedule.

  • No API key
  • Five fields and macros
  • Any IANA zone
  • GET or POST

Compute the next times

GET/cron/{expression}[/{count}[/{zone}]]

https://aisenseapi.com/services/v1/cron/0%209%20*%20*%201-5/3/Europe/Oslo

Ask when a schedule fires next

Put the expression in the path, percent-encoded: a space is %20 and the slash of a step such as */15 is %2F. The count and the zone follow; the zone may hold a slash of its own.

curl "https://aisenseapi.com/services/v1/cron/0%209%20*%20*%201-5/3/Europe/Oslo"

{"expression":"0 9 * * 1-5","zone":"Europe/Oslo",
 "from":{"timestamp":1794135600,"datetime":"2026-11-08T12:00:00+01:00","utc_datetime":"2026-11-08T11:00:00Z","weekday":"Sunday"},
 "count":3,
 "next":[
  {"timestamp":1794211200,"datetime":"2026-11-09T09:00:00+01:00","utc_datetime":"2026-11-09T08:00:00Z","weekday":"Monday"},
  {"timestamp":1794297600,"datetime":"2026-11-10T09:00:00+01:00","utc_datetime":"2026-11-10T08:00:00Z","weekday":"Tuesday"},
  {"timestamp":1794384000,"datetime":"2026-11-11T09:00:00+01:00","utc_datetime":"2026-11-11T08:00:00Z","weekday":"Wednesday"}
 ]}

Weekday mornings at nine, asked on a Sunday at noon: Monday, Tuesday and Wednesday come back, each as a timestamp, as local time with its offset, as UTC and with the name of the day.

The same question as JSON, with a fixed starting point so the answer is reproducible:

curl -X POST https://aisenseapi.com/services/v1/cron \
  -H "Content-Type: application/json" \
  -d '{"expression": "0 9 * * 1-5", "count": 3, "zone": "Europe/Oslo", "from": "2026-11-08T11:00:00Z"}'

Try it

Ask when an expression fires next, in UTC. Your browser posts it in a JSON field named expression, as the quick start does with POST.

What the five fields accept

FieldValuesAlso
minute0 to 59Lists such as 1,15,45, ranges such as 9-17, steps such as */15, 1-30/5 and 5/10, and * for every value.
hour0 to 23
day of month1 to 31
month1 to 12, or JAN to DEC
day of week0 to 7, or SUN to SAT; 0 and 7 are Sunday, and FRI-SUN runs through the weekend

The macros @hourly, @daily, @midnight, @weekly, @monthly, @yearly and @annually stand for their usual expressions, and the answer shows the expression they expanded to. @reboot names no time and is refused, and so is a six-field expression with seconds.

When both day fields are restricted, a day that matches either one fires, as cron has always done: 0 12 1 * 1 fires on the first of every month and on every Monday. When one of them starts with *, a day must match both: 0 12 */2 * 1 fires on odd-numbered days that are Mondays.

Time zones and the two odd nights

The zone is an IANA name such as Europe/Oslo or America/New_York, matched without regard to case, or UTC, which is the default. The timezones endpoint lists them. Every time in the answer is given three ways: the Unix timestamp, the local time with its UTC offset, and UTC.

On the night clocks spring forward, a local time that does not exist is skipped: 30 2 * * * in Oslo fires on 28 March 2026 and next on 30 March, since 29 March has no half past two. On the night clocks fall back, a repeated local time fires once. These are the choices most cron daemons make, and they are made here so that a schedule previewed on this endpoint behaves the way the daemon will.

What the free cron API endpoint returns

FieldTypeDescription
expressionstringThe five fields as read, with extra spaces folded and a macro expanded.
zonestringThe zone as PHP names it, so europe/oslo comes back as Europe/Oslo.
fromobjectThe starting point: the time given, or the time of the call. Every time in the answer is strictly after it.
countintegerHow many times the answer holds, 1 to 100. The search covers five years, so a yearly schedule asked for 100 times answers five.
nextarrayThe times in order, each with timestamp, datetime in the zone, utc_datetime and weekday.

In the JSON body from is Unix seconds or a date and time such as 2026-11-08T12:00:00Z; a text without an offset is read as UTC. The GET form always starts from now.

HTTP 400 when the expression cannot fire

curl -X POST https://aisenseapi.com/services/v1/cron \
  -H "Content-Type: application/json" \
  -d '{"expression": "0 0 30 2 *"}'
{"error":"The expression fires at no time within the next five years.","fix":"Five fields: minute, hour, day of month, month and day of week, with lists, ranges and steps; count 1 to 100; an IANA zone."}

Every refusal is HTTP 400 with error and fix: a field out of range, a step of zero, a range that runs backwards, an unknown month or weekday name, an unknown zone, a count outside 1 to 100, six fields, @reboot, or a day that never comes, such as the 30th of February.

Where a cron calculator earns its keep

Agents that plan

An agent given a schedule in words asks when it means, in the user's zone, before it commits to anything.

Preview before scheduling

Show the next five runs of an expression a person typed, then hand the interval to Webhook Schedule or to your own scheduler.

Auditing a crontab

Turn each line into its next dates and read them as a calendar instead of as five columns.

Tests with fixed time

Give from and the answer is the same every time, so a test can assert on it.

Privacy and limits

The expression travels in the path or the body and is not stored. The endpoint computes; it keeps no schedule and calls nothing, so there is nothing to cancel afterwards.

The service-wide limit is 5000 requests per IP per day, with no key and no account behind it. Every endpoint on the service is listed in the free public REST APIs reference, and the time API guide puts cron next to datetime, timestamps and time zones.