OpenCronAPI fires your HTTP webhooks exactly on schedule — and keeps firing them even when a server fails. Retries, timezone handling, alerts and execution logs are built in. No crontab, no server to babysit.
No credit card required · Free plan: 3 jobs · Set up in under a minute
A line in crontab works — until it doesn't. And when it fails, you're usually the last to know.
The server reboots, the box runs out of memory, a deploy wipes the crontab — and your job just stops. No error, no alert, no trace.
Did it run? Did it return 500? How long did it take? Plain cron tells you nothing. Debugging means SSH and log spelunking.
A single machine is a single point of failure. If it's down at 3 AM, the backup that depends on it simply never happens.
From zero to a production-grade scheduled job in minutes — via the API or the console.
Give us a URL, an HTTP method, and a schedule — an interval, a cron expression, or a one-off time. Add headers, a body, and auth if you need them.
Your job executes on a distributed node network with automatic failover. If a request fails, we retry it on your terms — exponential, linear or fixed.
Every run is logged with status, timing and response. Get an email or webhook the moment something fails. Pause, edit or trigger any job instantly.
No SDK required — it's just an HTTP request.
POST https://api.opencronapi.com/v1/jobs X-API-Key: your_api_key { "name": "Database backup", "url": "https://myapp.com/webhooks/backup", "method": "POST", "schedule_type": "cron", "cron_expression": "0 3 * * *", "timezone": "Europe/Prague", "retry_count": 3 }
Built for developers who can't afford missed jobs or unreliable infrastructure.
Jobs run on a distributed node network. If one node fails, another picks it up automatically — no single point of failure, no missed runs.
Intervals from 10 seconds to daily, full standard cron expressions, or one-off jobs — all timezone-aware, including DST.
Fixed, linear or exponential backoff, retry only on the status codes you choose, and automatic consecutive-failure tracking.
Every run captured: HTTP status, response time, headers and body preview. Replay, filter and export — up to 365 days of history.
Email and webhook notifications on failure, per job. Stop finding out about broken jobs from your customers.
A clean REST API for automation plus a visual console for humans — cron builder, response viewer, timelines. Both on every plan.
Because production scheduling needs more than a line in a file.
If it can be triggered by an HTTP request, OpenCronAPI can run it on schedule.
Start free. Upgrade only when you need more. No usage surprises.
We retry based on your configuration — fixed, linear or exponential backoff, on the status codes you choose. If every attempt fails, we mark the run as failed and send you an email or webhook alert.
Jobs are dispatched with sub-minute precision. You can schedule by interval (as low as 10 seconds on higher plans), by standard 5-field cron expression, or as a one-time run at a specific timestamp.
Yes. Standard 5-field cron plus shortcuts like @daily and @hourly, evaluated in the timezone you set per job — daylight-saving transitions included.
There is no server to maintain, and reliability is built in: distributed execution with failover, automatic retries, full logs, and failure alerts. A reboot or crashed box never silently kills your schedule.
Yes — import your existing jobs in one click from the console, or recreate them via the API. The free plan lets you try before you move anything.
Yes: 3 jobs, hourly scheduling, 7 days of logs, no credit card. Upgrade only when you need more jobs, tighter intervals or longer retention.
Schedule your first job in under a minute. Free plan, no card required.
Create your free accountOr read the docs first.
Part of the Open API ecosystem