The notification categories that an essential contact can be subscribed to. Each notification will be categorized by the sender into one of the following categories. All contacts that are subscribed to that category will receive the notification.

Values: NOTIFICATION_CATEGORY_UNSPECIFIED (0): Notification category is unrecognized or unspecified. ALL (2): All notifications related to the resource, including notifications pertaining to categories added in the future. SUSPENSION (3): Notifications related to imminent account suspension. SECURITY (5): Notifications related to security/privacy incidents, notifications, and vulnerabilities. TECHNICAL (6): Notifications related to technical events and issues such as outages, errors, or bugs. BILLING (7): Notifications related to billing and payments notifications, price updates, errors, or credits. LEGAL (8): Notifications related to enforcement actions, regulatory compliance, or government notices. PRODUCT_UPDATES (9): Notifications related to new versions, product terms updates, or deprecations. TECHNICAL_INCIDENTS (10): Child category of TECHNICAL. If assigned, technical incident notifications will go to these contacts instead of TECHNICAL.

SendTestMessageRequest

Request message for the SendTestMessage method.

UpdateContactRequest

Request message for the UpdateContact method.

ValidationState

A contact's validation state indicates whether or not it is the correct contact to be receiving notifications for a particular resource.

Values: VALIDATION_STATE_UNSPECIFIED (0): The validation state is unknown or unspecified. VALID (1): The contact is marked as valid. This is usually done manually by the contact admin. All new contacts begin in the valid state. INVALID (2): The contact is considered invalid. This may become the state if the contact's email is found to be unreachable.