Method: projects.findings.bulkMute Stay organized with collections Save and categorize content based on your preferences.
Kicks off an LRO to bulk mute findings for a parent based on a filter. The parent can be either an organization, folder or project. The findings matched by the filter will be muted after the LRO is done.
HTTP request
POST https://securitycenter.googleapis.com/v1/{parent=projects/*}/findings:bulkMuteThe URLs usegRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
parent |
Required. The parent, at which bulk action needs to be applied. Its format is |
Request body
The request body contains data with the following structure:
| JSON representation |
|---|
{"filter":string,"muteAnnotation":string,"muteState":enum ( |
| Fields | |
|---|---|
filter |
Expression that identifies findings that should be updated. The expression is a list of zero or more restrictions combined via logical operators Restrictions have the form The supported operators are:
The supported value types are:
|
muteAnnotation |
This can be a mute configuration name or any identifier for mute/unmute of findings based on the filter. |
muteState |
Optional. All findings matching the given filter will have their mute state set to this value. The default value is |
Response body
If successful, the response body contains an instance ofOperation.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/cloud-platform
For more information, see theAuthentication Overview.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-02 UTC.