Skip to main content
APIContext
Talk to salesStart free
Start HereGuidesConceptsCLIReferenceChangelogStatus

Alerts and Webhooks

An alert is a notification that fires when a monitor produces a result matching a trigger condition. Alerts connect APIContext to your incident-response toolchain so your team learns about problems without watching a dashboard.

Trigger conditions​

Each alert listens for one or more result categories:

TriggerWhen it fires
PassThe monitor met all conditions (useful for negative testing — alert when a call that should fail unexpectedly succeeds)
SlowThe response completed but exceeded a latency threshold
WarningThe response triggered a warning condition (by default, 4xx HTTP status)
ErrorThe response triggered an error condition (by default, 5xx HTTP status)
SLAThe call or workflow step exceeded its Service Level Objective for duration or another SLA metric

You can also set a failure threshold — for example, only fire after two consecutive failures — to reduce noise from transient issues.

Delivery channels​

APIContext delivers alerts to a wide range of platforms:

  • Email — simple but not recommended for high-volume scenarios
  • Webhooks — Slack, Microsoft Teams, PagerDuty, OpsGenie, VictorOps, BigPanda, Datadog, New Relic, StatusPage, and others
  • OpenTelemetry — the recommended default; sends structured telemetry to any OTLP-compatible backend (Axiom, Hydrolix, Honeycomb, etc.)

Each integration type has its own configuration fields (e.g., PagerDuty requires an integration key and severity level).

Scope: per-monitor vs. global​

Alerts can be configured on a single monitor or globally for every monitor in a project. Global alerts save setup time when you want the same notification rules across all endpoints.

Organization-wide alert suppression is also available from Organization settings, which disables all alerts until re-enabled.

See also​