Tickingora watches your jobs, crons and API endpoints. It expects a signal within a time window or checks your service itself. If something goes wrong, you get an alert.
Your job calls a secret URL when it finishes. No signal within the time window = alert.
We check your endpoint at the scheduled time — with authorization headers and three attempts.
Weekdays, Polish public holidays and your own excluded dates — no false alarms.
20 Heartbeat monitors, 3 HTTP Checks, e-mail alerts and 30 days of history.
The wizard guides you step by step and shows right away when Tickingora will expect a signal. No agents to install, no YAML to write.
Heartbeat when your job reports completion itself, or HTTP Check when we should check an endpoint.
Once a day, every hour or your own windows. Weekdays, Polish public holidays and excluded dates in one click.
Copy the ready-made curl command, or enter an HTTPS URL, the expected status and authorization headers.
Alerts go to your account e-mail and optionally a second address. Once it is fixed, you get a recovery notice.
You don't have to set up every job by hand. Your AI coding agent creates the monitor through the API and wires the Heartbeat into your app — exactly where the job succeeds. The docs are written with agents in mind: OpenAPI, llms.txt and a step-by-step guide.
„Add Tickingora monitoring of the daily payment import to my Laravel project. The import should finish between 6:00 and 7:00 on weekdays. Follow https://dev.tickingora.com/docs/agents.md”
GET /api/v1/monitors?external_id=shop:payment-import → nonePOST /api/v1/monitors → 201, window Mon–Fri 06:00–07:00TICKINGORA_PING_URL stored in the server secretsSchedule::command('payments:import')->onSuccess(ping)curl …?test=1 → OK (test signal, not counted)
The preview of the next five windows is computed by the same scheduler that later enforces them — weekdays, holidays, exclusions and daylight saving time included.
The state of every monitor, the result of the last run and ongoing incidents. Monitors in alarm are always at the top.
Number of signals, time of the first one, HTTP attempts with status codes and response times. No signal in a window means MISSED — no guessing whether the job was merely late.
Once saved, you get a secret URL and a ready command. A test signal checks the connection from your server without counting for a window or closing incidents.
Screenshots of the running app with sample data. The dashboard is currently available in Polish.
Free plan: 20 Heartbeat monitors, 3 HTTP Checks, e-mail alerts and 30 days of history.
Create a free account