Skip to main content
Causeloop keeps you informed through two complementary systems: a notifications feed that logs events relevant to you, and alert rules that proactively push signals to Slack, PagerDuty, or email when risk crosses a threshold you define.
This page covers the notifications feed and alert rule management. For notification delivery preferences (which channels you receive notifications on, and for which event types), see Settings → Notifications.

​
Notifications feed

​
Viewing your notifications

Click the bell icon in the top bar to open the notifications panel. The bell displays an unread badge count that updates in real time. The feed is available via GET /v1/me/notifications/feed. It supports:
ParameterDescription
unreadtrue to show only unread notifications
limitPage size (default 20)
cursorPagination cursor
Each notification item contains:
FieldDescription
idNotification ID
typeDot-separated event type (e.g. issue.escalated, prediction.alert.fired)
titleHuman-readable summary
readtrue if the notification has been read
created_atISO 8601 UTC timestamp

​
Notification types

TypeTrigger
issue.createdA new issue was ingested into your workspace
pattern.updatedA pattern you are watching was updated
prediction.alert.firedA prediction crossed an alert rule threshold
recommendation.createdA new recommendation was generated

​
Marking notifications read

Mark a single notification read Click the notification row to open the linked entity. The notification is marked read automatically. You can also call POST /v1/me/notifications/feed/{id}/read directly. Mark all notifications read Click Mark all read in the notifications panel header, or call: 
POST /v1/me/notifications/feed/read-all
{}
To clear only a specific category, pass a type prefix: 
POST /v1/me/notifications/feed/read-all
{ "type": "prediction." }
This returns { "marked": 8, "unread_count": 4 } — the count of items marked and the remaining unread count. Dismiss a notification Click the dismiss (×) button on a notification row, or call DELETE /v1/me/notifications/feed/{id}.

​
Unread count

The unread badge is driven by GET /v1/me/notifications/unread-count. The Dashboard bell icon uses the same endpoint to show the badge dot.

​
Alert rules

Alert rules let you define conditions on predictions or issues that trigger proactive notifications — before an incident occurs.

​
The Alert rules panel

Alert rules appear on the Predictions screen in a sidebar panel. Each rule shows:
  • Name — a human-readable label (e.g. “Critical pattern alert”)
  • Condition summary — threshold, window, and delivery channels (e.g. ≥85% / 3D · SLACK + PAGERDUTY)
  • Enabled toggle — click to enable or disable the rule without deleting it

​
Creating an alert rule

1

Open the Predictions screen

Navigate to Predictions in the left sidebar.
2

Click New alert rule

The rule creation dialog opens. (Alternatively, use the API directly — see below.)
3

Set the rule name

Enter a descriptive name, such as “Inventory N+1 watch”.
4

Define the scope

Choose which patterns or entity types this rule watches. Examples:
  • A specific pattern_id to watch one pattern
  • A workspace-wide rule that watches all predictions
5

Set the threshold

Enter the probability threshold (0.0–1.0) and the prediction window in days (≥ 1). The rule fires when any in-scope prediction exceeds this probability within the window.
6

Choose delivery channels

Select one or more channels: email, slack, pagerduty, or in_app. For Slack, configure the channel ID in your integration settings. For PagerDuty, configure the service key.
7

Save

The rule is active immediately. You can test it against live data using POST /v1/alert-rules/{id}/test.
The rule is created via POST /v1/alert-rules with a body such as: 
{
  "name": "Critical pattern alert",
  "scope": { "workspace": true },
  "threshold": {
    "probability": 0.85,
    "window_days": 3
  },
  "channels": ["slack", "pagerduty"],
  "severity": "critical"
}

​
Managing alert rules

ActionHow
List rulesGET /v1/alert-rules
Get a ruleGET /v1/alert-rules/{id}
Update a rulePATCH /v1/alert-rules/{id} — update name, threshold, channels, or enabled state
Delete a ruleDELETE /v1/alert-rules/{id}
Test a rulePOST /v1/alert-rules/{id}/test — evaluates the rule against current live predictions and returns whether it would fire
Snooze a rulePATCH /v1/alert-rules/{id}/snooze — suppress the rule for a duration (e.g. during a planned maintenance window)

​
Snoozing a rule

To silence an alert rule temporarily without deleting it: 
PATCH /v1/alert-rules/{id}/snooze
{
  "snoozed_until": "2026-06-20T09:00:00Z"
}
The rule resumes firing automatically after snoozed_until. To un-snooze early, send snoozed_until: null.

​
Alert rule fields

FieldTypeDescription
namestringRule display name (required, non-empty)
scopeobjectWhich patterns or entities the rule watches
threshold.probabilityfloatMinimum probability to trigger (0.0–1.0)
threshold.window_daysintegerPrediction window in days (≥ 1)
channelsstring[]Delivery channels: email, slack, pagerduty, in_app
severitystringAlert severity: critical, high, medium, low
enabledbooleanWhether the rule is active
snoozed_untilstring | nullISO timestamp; rule is silenced until this time

​
API reference

Notifications
EndpointDescription
GET /v1/me/notifications/feedPaginated notification feed
GET /v1/me/notifications/unread-countUnread badge count
POST /v1/me/notifications/feed/read-allMark all (or a category) read
POST /v1/me/notifications/feed/{id}/readMark a single notification read
DELETE /v1/me/notifications/feed/{id}Dismiss a notification
Alert rules
EndpointDescription
GET /v1/alert-rulesList workspace alert rules
POST /v1/alert-rulesCreate an alert rule
GET /v1/alert-rules/{id}Get an alert rule
PATCH /v1/alert-rules/{id}Update an alert rule
DELETE /v1/alert-rules/{id}Delete an alert rule
POST /v1/alert-rules/{id}/testTest rule against live data
PATCH /v1/alert-rules/{id}/snoozeSnooze a rule

Predictions

Alert rules fire on prediction thresholds — review the predictions screen.

Search & Activity

The activity feed shows all fired alerts as events.

Settings — Notifications

Configure which channels you receive notifications on and for which event types.