Draft a status page incident post
draft_incident_postUse this when the user wants to tell customers about a problem on one of their sites: declare a new incident, post an update on one, or resolve one. Returns the exact text, every status page it will appear on, how many subscribers, members and webhooks will be notified, and any conflict (such as an incident already open on that site), with a draft id. Saves the draft and posts nothing. Not for reading what happened: use get_incident.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | new declares an incident, update posts on an open one, resolve closes one. | |
| site | Yes | The site: its id, name or part of its URL. | |
| title | No | For new (needed, as on the Incidents tab): the incident's public title, as the user wants it shown. | |
| status | No | For update: where the incident stands. Default: its latest status. A new incident always starts as investigating. | |
| message | No | For new (needed): the first public message. For update: the update. For resolve: an optional closing message. | |
| incident | No | For update or resolve: the incident's id (list_incidents gives it). Leave out when the site has one open incident. | |
| severity | No | For new: critical (an outage: the site shows Down and the time counts as downtime), degraded (slow, or part of the site), or notify_only (shown, never counted as downtime, no subscriber email). Default critical, as the Incidents tab's form starts. | |
| components | No | For new: what the incident is about: site for the site itself (the default), or a dependency, content check or cron job of it by name or id. The first check named decides the incident's type. | |
| internal_only | No | For update: a note only the team sees; no status page shows it and nobody is emailed. |