Comment on Incident
Adds a comment to the timeline of an Incident Management incident.
POST /api/im/incidents/:id/comment
Adds a free-text comment to the incident's timeline (an event of kind comment, visible in events of Get Incident). Outbound integrations are notified of the comment, and subscribers of a status page driven by a status page rule may receive it as an update. Comments are accepted on closed incidents too.
Authentication
Any IM-eligible role (admin, editor, responder) or an organization-wide API token, see Authentication. Incident Management must be enabled for the organization. There is no team restriction.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Comment text, not blank, up to 10,000 characters. |
Example (cURL)
curl -X POST "$BASE_URL/api/im/incidents/42/comment" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{ "text": "Failover to the replica is running, ETA 10 minutes." }'Response
200 OK
{
"ok": true
}Common errors
401 Unauthorizedwhen not authenticated403 Forbidden(customerScopedTokenForbidden) when using a customer-scoped token403 Forbidden(imAccessDenied) when the session user has no IM-eligible role403 Forbidden(imNotEnabled) when Incident Management is not enabled for the organization400 Bad Request(invalidRequestBody) when:idis not a positive integer, ortextis missing, blank or longer than 10,000 characters404 Not Found(imIncidentNotFound) when the incident does not exist, or belongs to another organization
Assign Incident Roles
Sets the holder of an incident role (commander, tech lead, comms, assignee), or adds an extra responder to an Incident Management incident, optionally paging them.
Merge Incidents
Merges one Incident Management incident into another: its alerts and timeline move over, and the merged incident stops escalating.