DOCS

Events reference

All system events emitted by HOWLOPS — webhook events, WebSocket events, and in-app feed events.

HOWLOPS events are emitted in three delivery channels:

Webhook — HTTP POST to your endpoint (Webhooks reference)
WebSocket — WSS /api/v1/ws real-time stream
In-app notification feed — /api/v1/notifications/feed

Webhook events

Event	Trigger
`incident.created`	Monitor or heartbeat opens an incident
`incident.acknowledged`	Team member acknowledges the incident
`incident.resolved`	Incident resolved (auto-recovery or manual)
`monitor.status_changed`	Monitor transitions between `up`, `down`, `paused`
`heartbeat.missed`	Heartbeat not received within grace period
`heartbeat.recovered`	Heartbeat received after a missed period
`maintenance.started`	Maintenance window begins
`maintenance.ended`	Maintenance window ends
`test`	Manual test delivery from UI

WebSocket events

Connect to WSS /api/v1/ws?token=<access_token>. Each message is a JSON object with a type field.

`incident_update`

{
  "type": "incident_update",
  "data": {
    "incident_id": "uuid",
    "monitor_id": "uuid",
    "status": "open | acknowledged | resolved",
    "severity": "critical | warning | info",
    "updated_at": "ISO 8601"
  }
}

`monitor_status`

{
  "type": "monitor_status",
  "data": {
    "monitor_id": "uuid",
    "status": "up | down | paused",
    "response_time_ms": 142,
    "checked_at": "ISO 8601"
  }
}

`heartbeat_status`

{
  "type": "heartbeat_status",
  "data": {
    "heartbeat_id": "uuid",
    "status": "up | missed",
    "last_ping_at": "ISO 8601 | null"
  }
}

`ping`

{ "type": "ping" }

The server sends a ping every 30 seconds. Reply with { "type": "pong" } to keep the connection alive.

In-app notification feed events

Returned by GET /api/v1/notifications/feed (paginated).

`event_type`	Meaning
`incident_opened`	New incident opened
`incident_acked`	Incident acknowledged
`incident_resolved`	Incident resolved
`monitor_recovered`	Monitor back to `up`
`heartbeat_missed`	Heartbeat grace period elapsed
`heartbeat_recovered`	Heartbeat resumed
`maintenance_started`	Maintenance window started
`maintenance_ended`	Maintenance window ended
`system`	Platform announcement or broadcast

Feed item shape:

{
  "id": "uuid",
  "event_type": "incident_opened",
  "title": "Production API is down",
  "body": "Monitor detected failure at 10:00 UTC",
  "read": false,
  "created_at": "ISO 8601",
  "link": "/monitors/uuid/incidents/uuid"
}

Severity levels

Severity	Description
`critical`	Service is fully unavailable or data loss is possible
`warning`	Service is degraded, slow responses, or partial failures
`info`	Informational — recovery, maintenance, or system notices