Method: legacyCases.isCustomCaseExists

Full name: projects.locations.instances.legacyCases.isCustomCaseExists

Checks if a custom simulated case with a specific alert name already exists. This is useful for avoiding duplicate simulation definitions.

HTTP request


GET https://chronicle.africa-south1.rep.googleapis.com/v1alpha/{name}/legacyCases:isCustomCaseExists

Path parameters

Parameters
name

string

Required. The resource name of the LegacyCase to retrieve. Format: projects/{project}/locations/{location}/instances/{instance}/LegacyCases

Query parameters

Parameters
alertName

string

Required. The name of the custom case to check.

Request body

The request body must be empty.

Response body

Response message for legacyCases.isCustomCaseExists.

If successful, the response body contains data with the following structure:

JSON representation
{
  "payload": boolean
}
Fields
payload

boolean

Output only. True if the custom case exists, false otherwise.

Authorization scopes

Requires one of the following OAuth scopes:

  • https://www.googleapis.com/auth/cloud-platform
  • https://www.googleapis.com/auth/chronicle
  • https://www.googleapis.com/auth/chronicle.readonly

For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the name resource:

  • chronicle.legacyCases.getSimulated

For more information, see the IAM documentation.