Webhooks
Webhooks are how Seiri receives heartbeats and events. Every monitor lives under Core → Webhooks in the dashboard.
Webhook Types
Seiri supports three types (exact product names):
1. Periodic
- Expect a check-in every fixed interval (e.g. every 60 seconds).
- Use for heartbeats and continuous health signals.
- Missed windows alert after the grace period.
2. Cron
- Expect a check-in on a cron expression schedule (e.g.
30 2 * * *). - Use for nightly backups, ETL, digests, and other wall-clock jobs.
- Drift and missed runs show under Services → Cron Jobs as well as webhook stats.
3. On-Demand
- No schedule — ping only when an event happens (manual / event-driven).
- Use for ad-hoc notifications and one-shot signals.
- Does not alert for “missed” runs (there is no expected cadence).
There is no type named Immediate or Scheduled. Use On-Demand and Cron.
Endpoint ID and ping URL
Each webhook has an endpoint ID:
<org-slug>:<webhook-ref>
Example: acme-demo:deno-xFY-7Yv
Copy it from the ENDPOINT column (copy button) or from webhook details (endpoint_url).
Ping URLs (ingest host is always ping.seiri.app):
https://ping.seiri.app/webhook/<endpoint-id>
https://ping.seiri.app/webhook/<endpoint-id>/success
https://ping.seiri.app/webhook/<endpoint-id>/fail
GET or POST. Empty body is fine.
Events overview
- All check-ins for a webhook are grouped under that webhook.
- Events include success / failure status, timestamp, and optional payload.
- Open webhook stats (bar-chart icon) or the webhook detail page to inspect history.
Tip: Use Periodic or Cron for job monitoring; use On-Demand when there is no expected schedule.