Resolve incident
Mark an incident as resolved.
Restrictions
Usage
- When a resolution 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 resolve 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 resolving one or more incidents.
Incident IDs to resolve. At most 100 per call.
1 - 100 elements^[0-9a-fA-F]{24}$Optional root cause note applied to every resolved incident.
1024Optional resolution note applied to every resolved incident.
1024New incident description, up to 6,144 characters. When set, it replaces the current description before the incident closes.
6144Custom field values for the resolution form. Allowed keys and values depend on the incident's visible form.
Images attached to the resolution timeline entry.
Form summary recorded as a timeline comment. Accepted only when the resolution 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.