Add an update to an incident.
const url = 'https://api.siteqwality.com/incident/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/update';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"status":"investigating","message":"example","visibility":"public","notify_subscribers":true,"force":true}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.siteqwality.com/incident/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/update \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "status": "investigating", "message": "example", "visibility": "public", "notify_subscribers": true, "force": true }'Public by default: it sets the public status (omitted keeps it), resolved resolves,
and moving backwards returns 409 unless force is set. With notify_subscribers the
subscribers of every page it is published on are emailed. An internal update shows
only in the app and never changes the public status.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Incident identifier
Request Body required
Section titled “Request Body required ”object
Email status page subscribers about a public update. Default true on the status page
route (that page only), false on /incident/{id}/update (true there emails every page).
Post even when this moves the status backwards (otherwise 409).
Responses
Section titled “ Responses ”Incident update added
object
The public status when it was posted.
public updates show on status pages; internal ones only here.
Who posted it; null for the system, API keys and older updates.
Example
{ "status": "investigating", "visibility": "public"}Invalid request body, or an internal update with status resolved
Missing or invalid authentication
Incident not found
The status would move backwards, or the incident is resolved; data holds its current state
Internal server error