Method: projects.findings.bulkMute

Kicks off an LRO to bulk mute findings for a parent based on a filter. If no location is specified, findings are muted in global. 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


The URL uses gRPC Transcoding syntax.

Path parameters



Required. The parent, at which bulk action needs to be applied. If no location is specified, findings are updated in global. The following list shows some examples:

  • organizations/[organization_id]
  • organizations/[organization_id]/locations/[locationId]
  • folders/[folder_id]
  • folders/[folder_id]/locations/[locationId]
  • projects/[projectId]
  • projects/[projectId]/locations/[locationId]

Request body

The request body contains data with the following structure:

JSON representation
  "filter": string


Expression that identifies findings that should be updated. The expression is a list of zero or more restrictions combined via logical operators AND and OR. Parentheses are supported, and OR has higher precedence than AND.

Restrictions have the form <field> <operator> <value> and may have a - character in front of them to indicate negation. The fields map to those defined in the corresponding resource.

The supported operators are:

  • = for all value types.
  • >, <, >=, <= for integer values.
  • :, meaning substring matching, for strings.

The supported value types are:

  • string literals in quotes.
  • integer literals without quotes.
  • boolean literals true and false without quotes.

Response body

If successful, the response body contains an instance of Operation.

Authorization scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.