Rootly

Rootly is a Slack-native incident management platform that automates the coordination overhead of incidents: auto-creates Slack channels, pages responders, tracks timelines, manages role assignments (incident commander, comms lead), and generates retrospective drafts. Its REST API enables programmatic incident creation and management for agents that need to: open incidents from automated alerts, add timeline events from monitoring tools, update incident status, or query incident reports for analysis. Clean REST design with good documentation. Backed by engineering teams at recognized companies. Confidence is docs-derived.

REST API at api.rootly.com/v1. Resources: incidents, incident_events, incident_roles, incident_types, severities, teams, services, on_call_schedules. POST /v1/incidents creates an incident (title, severity, team, service). POST /v1/incidents/{id}/incident_events adds a timeline event. PATCH /v1/incidents/{id} updates status (mitigated, resolved). GET /v1/incidents lists all incidents with filtering by status, team, service, date range. Response payloads are JSON-API format with data, attributes, and relationships. Pagination via cursor.

Bearer token auth via Authorization: Bearer header using API key from Rootly organization settings. Keys are org-scoped with full access. No per-resource token scoping. Rootly also supports Slack OAuth for user-facing flows. HTTPS enforced. API keys managed in Settings → API Access. No published token expiry for API keys; rotation recommended per internal policy.

JSON-API error format with errors array containing title, detail, and status. 401 for invalid token, 404 for missing incident, 422 for validation errors (missing required fields). Incident status transitions validated (e.g., can't move from open directly to resolved without mitigation step, depending on config). Rate limits documented per plan. Rootly SaaS uptime at status.rootly.com. Webhook support for incident lifecycle events (creation, update, resolution).

rootly.com/api provides API reference with full endpoint documentation, authentication guide, and data model overview. Getting started requires a Rootly account (team plan or higher for API access). Integration guides for PagerDuty, OpsGenie, StatusPage, and monitoring tools available. SDKs not officially published; REST is the integration surface. Changelog and API versioning policy documented. Enterprise support for self-hosted/air-gapped deployments.