Dismiss Merge Suggestion

POST /api/im/incidents/:id/dismiss-merge-suggestion

When an incident is created, Incident Management looks for open incidents from other alert sources of your organization that are probably the same (same service or same host, triggered within 15 minutes) and lists them in mergeSuggestions of Get Incident. Nothing is merged automatically. This endpoint drops one suggestion when it is wrong; to accept it, use Merge Incidents instead.

The dismissal is written to the incident timeline (merge_suggestion_dismissed, payload { targetIncidentId }) and to the organization audit log. Neither incident is changed otherwise, nobody is notified.

AuthenticationCopy Anchor Link

Any IM-eligible role or an organization-wide API token, see Authentication. Same rights as merging: you must be a member of the team of incident :id or an organization admin.

Request BodyCopy Anchor Link

curl -X POST "$BASE_URL/api/im/incidents/43/dismiss-merge-suggestion" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "targetIncidentId": 41 }'

ResponseCopy Anchor Link

200 OK:

{ "ok": true }

Common errorsCopy Anchor Link

• 401 Unauthorized when not authenticated
• 403 Forbidden (imTeamMembershipRequired) when you are not a member of the incident's team and not an organization admin
• 400 Bad Request (invalidRequestBody) when targetIncidentId is missing, not a positive integer, or the body has other fields
• 404 Not Found (imIncidentNotFound) when the incident does not exist or belongs to another organization
• 404 Not Found (imMergeSuggestionNotFound) when the incident has no open suggestion for targetIncidentId (never suggested, or already dismissed)