---
title: "Mute or unmute security findings"
method: PATCH
path: "/api/v2/security/findings/mute"
tags: ["Security Monitoring"]
---

# Mute or unmute security findings

`PATCH /api/v2/security/findings/mute`

Mute or unmute security findings.
You can mute or unmute up to 100 security findings per request. The request body must include `is_muted` and `reason` attributes. The allowed reasons depend on whether the finding is being muted or unmuted:
  - To mute a finding: `PENDING_FIX`, `FALSE_POSITIVE`, `OTHER`, `NO_FIX`, `DUPLICATE`, `RISK_ACCEPTED`.
  - To unmute a finding: `NO_PENDING_FIX`, `HUMAN_ERROR`, `NO_LONGER_ACCEPTED_RISK`, `OTHER`.

## Request body

- MuteFindingsRequest — Request to mute or unmute security findings.
  - `data` MuteFindingsRequestData, required — Data of the mute request.
    - `attributes` MuteFindingsRequestDataAttributes, required — Attributes of the mute request.
      - `mute` MuteFindingsMuteAttributes, required — Mute properties to apply to the findings.
        - `description` string — Additional information about the reason why the findings are muted or unmuted. This field has a limit of 280 characters.
        - `expire_at` integer — The expiration date of the mute action (Unix ms). It must be set to a value greater than the current timestamp. If this field is not provided, the findings remain muted indefinitely.
        - `is_muted` boolean, required — Whether the findings should be muted or unmuted.
        - `reason` 'PENDING_FIX' | 'FALSE_POSITIVE' | 'OTHER' | 'NO_FIX' | 'DUPLICATE' | 'RISK_ACCEPTED' | 'NO_PENDING_FIX' | 'HUMAN_ERROR' | 'NO_LONGER_ACCEPTED_RISK', required — The reason why the findings are muted or unmuted.
    - `id` string — Unique identifier of the mute request.
    - `relationships` MuteFindingsRequestDataRelationships, required — Relationships of the mute request.
      - `findings` Findings, required — A list of security findings.
        - `data` FindingData[] — Array of security finding data objects.
          - `id` string, required — Unique identifier of the security finding.
          - `type` 'findings', required — Security findings resource type.
    - `type` 'mute', required — Mute resource type.

## Response `202`

Accepted

- MuteFindingsResponse — Response for the mute or unmute request.
  - `data` MuteFindingsResponseData — Data of the mute response.
    - `id` string, required — Unique identifier of the mute request.
    - `type` 'mute', required — Mute resource type.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `404` — Not Found
- `422` — Unprocessable Entity
- `429` — Too many requests

---

[API](https://skmtc.net/datadog/apis/api-v2.md) · [All operations](https://skmtc.net/datadog/apis/api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/datadog/api-v2/versions/da68bf029e4c/schema)