Supercheck LogoSupercheck
AI SRE

Declare an incident

POST
/api/sre/incidents

Opens an incident by hand, with the same numbering, timeline, notifications and re-notify as alert-opened incidents. Only title and severity are needed. Affected monitors (or monitors mapped to affected services) attach their next alerts to this incident instead of opening a new one. With statusPage, a linked public incident is posted after the incident is saved; if that post fails the incident is kept and the response carries warning status_page_failed. Limited to 10 per minute per user and 60 per hour per organization.

Authorization

bearerAuth
headerAuthorizationBearer <token>

Project-scoped CLI token (sck_live_* or sck_test_*) for documented API operations that accept bearer authentication. Interactive browser operations may require a session cookie. Trigger keys (sck_trigger_* / legacy job_*) are accepted only by job trigger endpoints.

Request Body

application/json
  1. body
title*string
Length1 <= length <= 500
severity?string
Default"sev3"
Value in"sev1""sev2""sev3""sev4"
summary?string
Lengthlength <= 4000
primaryServiceId?string

The service's owner becomes the assignee; otherwise the caller

Formatuuid
affected?

At most 50 services and monitors in all, including primaryServiceId

commanderUserId?string

A project editor or admin

Formatuuid
statusPage?

Needs status page update permission

Response Body

Incident declared

application/json
  1. response
success?boolean
incident?
statusPageIncidentId?string
Formatuuid
warning?"status_page_failed"
Value in"status_page_failed"
Example Request
curl -X POST 'https://app.supercheck.io/api/sre/incidents' \  -H 'Content-Type: application/json' \  -d '{  "title": "string"}'
Example Response
{  "success": true,  "incident": {    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "incidentNumber": 0,    "title": "string"  },  "statusPageIncidentId": "fea3232e-2398-49d1-b0b2-98b94148fa18",  "warning": "status_page_failed"}