API Reference google_api_alert_center v0.14.0
Modules
API client metadata for GoogleApi.AlertCenter.V1beta1.
API calls for all endpoints tagged Alerts
.
API calls for all endpoints tagged V1beta1
.
Handle Tesla connections for GoogleApi.AlertCenter.V1beta1.
Alerts for user account warning events.
The details of the login action.
Alerts from Google Workspace Security Center rules service configured by an admin.
Alerts from App Maker to notify admins to set up default SQL instance.
Requests for one application that needs default SQL setup.
Attachment with application-specific information about an alert.
A representation of a CSV file attachment, as a list of column headers and a list of data rows.
A representation of a single data row in a CSV file.
Alert for setting the domain or IP that malicious email comes from as whitelisted domain or IP in Gmail advanced settings.
A mobile device compromised alert. Derived from audit logs.
Detailed information of a single MDM device compromised event.
Alerts that get triggered on violations of Data Loss Prevention (DLP) rules.
Domain ID of Gmail phishing alerts.
A takeout operation for the entire domain was initiated by an admin. Derived from audit logs.
Details of a message in phishing spike alert.
An incident reported by Google Operations for a Google Workspace application.
Proto for all phishing alerts with common payload. Supported types are any of the following: User reported phishing User reported spam spike Suspicious message reported Phishing reclassification Malware reclassification Gmail potential employee spoofing
Entity whose actions triggered a Gmail phishing alert.
Alert for a spike in user reported phishing. Warning: This type has been deprecated. Use MailPhishing instead.
Common alert information about violated rules that are configured by Google Workspace administrators.
Metadata related to the action.
Proto that contains match information from the condition part of the rule.
Detector provided by Google.
Detector defined by administrators.
Proto that contains resource information.
Proto that contains rule information.
A state-sponsored attack alert. Derived from audit logs.
A mobile suspicious activity alert. Derived from audit logs.
Detailed information of a single MDM suspicious activity event.
An alert affecting a customer.
A customer feedback about an alert.
A request to perform batch delete on alerts.
Response to batch delete operation on alerts.
A request to perform batch undelete on alerts.
Response to batch undelete operation on alerts.
Response message for an alert feedback listing request.
Response message for an alert listing request.
Customer-level settings.
Settings for callback notifications. For more details see Google Workspace Alert Notification.
A reference to a Cloud Pubsub topic. To register for notifications, the owner of the topic must grant alerts-api-push-notifications@system.gserviceaccount.com
the projects.topics.publish
permission.
A request to undelete a specific alert that was marked for deletion.
A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for Empty
is empty JSON object {}
.
The Status
type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status
message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.