Acknowledge incident
Acknowledge an incident to indicate you are actively working on it.
Restrictions
Usage
- When an acknowledgement form applies,
custom_fields,summary, andimagesmust match its visible elements and required rules. - For a batch, form values are accepted only when every selected incident resolves to the same form; otherwise acknowledge incidents individually.
- The legacy
valuesandcustom_valuesproperties are rejected; usecustom_fields. - Audited — changes are recorded in the audit log.
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 acknowledging one or more incidents.
Incident IDs to acknowledge. At most 100 per call.
1 - 100 elements^[0-9a-fA-F]{24}$Custom field values for the acknowledgement form. Allowed keys and values depend on the incident's visible form.
Images attached to the acknowledgement timeline entry.
Form summary recorded as a timeline comment. Accepted only when the acknowledgement form contains a summary element.
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.