Incident Management

Incident Management (IM) is a separate domain from Monitoring: a two-level alert/incident model with teams, on-call schedules, and escalation policies. This section covers the public REST endpoints for ingesting alerts and managing incidents.

Authentication

Every endpoint below requires an organization-wide API token:

BASE_URL="https://uptimeify.io"
TOKEN="wsm_<your-organization-wide-api-token>"

Create one via Create Organization Token and leave customerId unset. A token created with a customerId (a customer-scoped token) is always rejected with 403 Forbidden (imAccessDenied); Incident Management has no customer-facing surface, by design.

Incident Management must also be activated for your organization, or every endpoint below returns 403 Forbidden (imNotEnabled).

Endpoints

• Events Ingest: POST /api/im/events
• List Incidents: GET /api/im/incidents
• Get Incident: GET /api/im/incidents/:id
• Create Incident: POST /api/im/incidents
• Acknowledge / Update Incident Status: POST /api/im/incidents/:id/status
• Resolve Incident: POST /api/im/incidents/:id/resolve
• Teams: GET /api/im/teams
• Schedules: GET/POST /api/im/schedules
• Schedule Overrides: GET/POST /api/im/schedules/:id/overrides
• Who Is On Call: GET /api/im/on-call

Alert source setup guides

Prefer to send alerts from an existing monitoring tool instead of calling the API directly? See the alert source setup guides for step-by-step instructions for Zabbix, Datadog, Grafana Alerting, Prometheus Alertmanager, Sentry, and any custom webhook. Each uses its own per-source ingest URL (POST /api/im/ingest/:token), separate from the Events Ingest endpoint above.

Error codes

See Error codes and known API pitfalls for the full list of data.code values these endpoints can return.