Add comment to incident
Add a text comment to the incident timeline.
Restrictions
Usage
- To mention a member, embed a markdown link in
commentin the form[@Display Name](flashduty://ref/member/<member_id>). Mentioned members receive a dedicated personal notification, which is not affected bymute_reply. - Plain
@nametext without the link syntax does not create a mention. - The server rewrites each mention’s display label to the member’s canonical name.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Parameters for adding a comment to one or more incidents.
Incident IDs to comment on. At most 100 per call.
1 - 100 elements^[0-9a-fA-F]{24}$Comment body. Leading and trailing whitespace is trimmed; the comment must be non-empty after trimming and at most 1024 characters (counted after @mention normalization).
1024When true, do not trigger webhook reply actions for this comment.
Optional ID of an account-level comment type to attach to the comment (MongoDB ObjectID). An invalid or all-zero ID is rejected with 400.
^[0-9a-fA-F]{24}$Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.