tickingora. API docs OpenAPI llms.txt tickingora.com Get an API key

Incidents & alerts

Run results

Status Monitor type Meaning
waiting Heartbeat The window is planned or open, no signal yet.
scheduled HTTP The check is planned.
running HTTP Attempts in progress.
success both A signal arrived in the window / a response met expected_status.
missed Heartbeat No signal until the end of the window.
failed HTTP All attempts failed.
not_executed HTTP Tickingora could not run the check on time — not your fault, no alert.
unknown Heartbeat Tickingora was down during the window — not your fault, no alert.

Finished results are permanent: a later success never rewrites a missed window.

Incidents

  1. The first missed or failed result opens an incident and sends one alert.
  2. Further failures while the incident is open are recorded (failed_runs_count) but do not send more e-mails.
  3. The first later successful scheduled window or check — or a successful recovery check — closes it as recovered and sends a recovery e-mail.
  4. Pausing a monitor closes an open incident as closed, without an e-mail.

A monitor has at most one open incident (open_incident in the monitor response).

Recipients

Alerts go to the account e-mail and optionally one extra address (notifications.extra_email). Each kind can be switched off with notifications.on_failure and notifications.on_recovery. Alerts are sent from tick@tickingora.com.

Confirming the extra address

Nobody can be signed up for alerts by someone else:

  1. When a monitor is saved with a new extra address, Tickingora sends that address a confirmation e-mail (from hello@tickingora.com).
  2. The address receives alerts only after its owner confirms (the link opens a page with a button — mail scanners that open links cannot confirm on anyone's behalf). Links expire after 7 days.
  3. Every alert to the extra address has an unsubscribe link. An unsubscribed address gets no alerts and no further confirmation requests from that account.

notifications.extra_email_status shows pending, verified or unsubscribed. A confirmed address is confirmed for all monitors of the account. Until then the dashboard shows a notice listing every address that does not receive alerts yet, with the monitors using it.

Confirmation e-mails are limited to one per hour per address when a monitor is saved, a manual resend from the dashboard once per 10 minutes, and 10 per account per 24 hours. The dashboard always shows the real time of the next allowed request, taking all limits into account.

Delivery is idempotent: a retried job never sends the same alert twice. The dashboard shows each delivery and whether the mail provider accepted it (acceptance is not the same as the message being read).