Help Center/ Cloud Trace Service/ API Reference (Ally Region)/ APIs/ Key Event Notification Management/ Creating a Key Event Notification

Updated on 2026-01-04 GMT+08:00

View PDF

Creating a Key Event Notification

Function

This API is used to configure notifications for key events. When specified operations are detected, the system uses Simple Message Notification (SMN) topics to notify users via SMS, email, or HTTP/HTTPS messages. This helps you detect high-risk operations promptly. These notifications can also be used as triggers for specific operations or be integrated with your own audit systems.

Calling Method

For details, see Calling APIs.

URI

POST /v3/{project_id}/notifications

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details, see Obtaining an Account ID and Project ID.

Request Parameters

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
notification_name	Yes	String	Key event notification name.
operation_type	Yes	String	Operation type. Possible options include complete and customized. If you choose complete, operations and notify_user_list parameters are not required, and notifications will be triggered for any supported operation on any connected cloud service. If you choose customized, notifications will only be sent when the specific operations defined in operations occur.
operations	No	Array of Operations objects	Operation list.
notify_user_list	No	Array of NotificationUsers objects	List of users whose operations will trigger notifications. Currently, up to 50 users in 10 user groups can be configured.
topic_id	No	String	SMN topic URN or FunctionGraph function URN. To obtain the topic URN, call the SMN API for querying topics. Example URN: urn:smn:regionId:f96188c7ccaf4ffba0c9aa149ab2bd57:test_topic_v2 To obtain the function URN, call the FunctionGraph API for querying functions. Example URN urn:fss:xxxxxxxxx:7aad83af3e8d42e99ac194e8419e2c9b:function:default:test
filter	No	Filter object	Advanced filter of the key event notification.
agency_name	No	String	Cloud service agency name. If this parameter is set to cts_admin_trust, a cloud service agency named cts_admin_trust is automatically created during key event notification creation.

**Table 3** Operations
Parameter	Mandatory	Type	Description
service_type	Yes	String	Cloud service. The value must be the uppercase acronym of a cloud service connected with CTS. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in Cloud Trace Service User Guide. You can click the document link of each cloud service to view its acronym.
resource_type	Yes	String	Resource type.
trace_names	Yes	Array of strings	Trace name.

**Table 4** NotificationUsers
Parameter	Mandatory	Type	Description
user_group	Yes	String	IAM user group.
user_list	Yes	Array of strings	IAM user.

**Table 5** Filter
Parameter	Mandatory	Type	Description
condition	Yes	String	Relationship between conditions. AND (default): The rule is triggered only if all specified filtering criteria are met. OR: The rule is triggered if at least one of the filtering criteria is met.
is_support_filter	Yes	Boolean	Whether to enable the advanced filter.
rule	Yes	Array of strings	Advanced filter criteria rule. Example: key != value. Format: field rule value- Field value range: api_version, code, trace_rating, trace_type, resource_id, and resource_name.- Rule: != or =.- Value: api_version: ^(a-zA-Z0-9_-.){1,64}$; code: 1 to 256 characters; trace_rating: normal, warning, or incident; trace_type: *ConsoleAction, ApiCall, or SystemAction; *resource_id: 1 to 350 characters; resource_name: 1 to 256 characters.

Response Parameters

Status code: 201

**Table 6** Response body parameters
Parameter	Type	Description
notification_name	String	Notification name.
operation_type	String	Operation type. Possible options include complete and customized. complete: Notifications will be sent via SMN for all operations recorded by CTS. customized: Notifications will be sent via SMN only for specified operations performed on specified cloud services.
operations	Array of Operations objects	Operation list.
notify_user_list	Array of NotificationUsers objects	List of users whose operations will trigger notifications. Currently, up to 50 users in 10 user groups can be configured.
status	String	Notification status. Possible options include disabled and enabled. disabled: The key event notification is disabled. enabled: The key event notification is enabled.
topic_id	String	Unique resource ID of an SMN topic. You can obtain the ID by querying the topic list.
notification_id	String	Unique notification ID.
notification_type	String	Notification type. smn: SMN fun: FunctionGraph
project_id	String	Project ID.
create_time	Long	Time when a notification rule was created.
filter	Filter object	Advanced filter of the key event notification.
agency_name	String	Cloud service agency name. If this parameter is set to cts_admin_trust, a cloud service agency named cts_admin_trust is automatically created during key event notification creation.

**Table 7** Operations
Parameter	Type	Description
service_type	String	Cloud service. The value must be the uppercase acronym of a cloud service connected with CTS. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in Cloud Trace Service User Guide. You can click the document link of each cloud service to view its acronym.
resource_type	String	Resource type.
trace_names	Array of strings	Trace name.

**Table 8** NotificationUsers
Parameter	Type	Description
user_group	String	IAM user group.
user_list	Array of strings	IAM user.

**Table 9** Filter
Parameter	Type	Description
condition	String	Relationship between conditions. AND (default): The rule is triggered only if all specified filtering criteria are met. OR: The rule is triggered if at least one of the filtering criteria is met.
is_support_filter	Boolean	Whether to enable the advanced filter.
rule	Array of strings	Advanced filter criteria rule. Example: key != value. Format: field rule value- Field value range: api_version, code, trace_rating, trace_type, resource_id, and resource_name.- Rule: != or =.- Value: api_version: ^(a-zA-Z0-9_-.){1,64}$; code: 1 to 256 characters; trace_rating: normal, warning, or incident; trace_type: *ConsoleAction, ApiCall, or SystemAction; *resource_id: 1 to 350 characters; resource_name: 1 to 256 characters.

Status code: 400

**Table 10** Response body parameters
Parameter	Type	Description
error_code	String	Error code. Format: CTS.XXX.
error_msg	String	Error message.

Status code: 401

**Table 11** Response body parameters
Parameter	Type	Description
error_code	String	Error code. Format: CTS.XXX.
error_msg	String	Error message.

Status code: 403

**Table 12** Response body parameters
Parameter	Type	Description
error_code	String	Error code. Format: CTS.XXX.
error_msg	String	Error message.

Status code: 404

**Table 13** Response body parameters
Parameter	Type	Description
error_code	String	Error code. Format: CTS.XXX.
error_msg	String	Error message.

Status code: 500

**Table 14** Response body parameters
Parameter	Type	Description
error_code	String	Error code. Format: CTS.XXX.
error_msg	String	Error message.

Status code: 503

**Table 15** Response body parameters
Parameter	Type	Description
error_code	String	Error code. Format: CTS.XXX.
error_msg	String	Error message.

Example Requests

Create a complete key event notification.

POST https://{endpoint}/v3/{project_id}/notifications

{
  "notification_name" : "test",
  "filter" : {
    "is_support_filter" : true,
    "rule" : [ "code != 200", "api_version = v1.0", "trace_rating = normal", "trace_type != ApiCall", "resource_id = xxx", "resource_name = xxx" ],
    "condition" : "OR"
  },
  "operation_type" : "complete",
  "agency_name" : "cts_admin_trust",
  "topic_id" : "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:test"
}

Create a custom key event notification.

POST https://{endpoint}/v3/{project_id}/notifications

{
  "notification_name" : "test",
  "operation_type" : "customized",
  "agency_name" : "cts_admin_trust",
  "filter" : {
    "is_support_filter" : true,
    "rule" : [ "code != 200", "api_version = v1.0", "trace_rating = normal", "trace_type != ApiCall", "resource_id = xxx", "resource_name = xxx" ],
    "condition" : "OR"
  },
  "operations" : [ {
    "service_type" : "CTS",
    "resource_type" : "tracker",
    "trace_names" : [ "createTracker", "deleteTracker" ]
  }, {
    "service_type" : "CTS",
    "resource_type" : "notification",
    "trace_names" : [ "deleteNotification", "updateNotification" ]
  }, {
    "service_type" : "AOM",
    "resource_type" : "pe",
    "trace_names" : [ "deletePolicyGroup", "updatePolicyGroup", "createPolicyGroup" ]
  } ],
  "notify_user_list" : [ {
    "user_group" : "admin",
    "user_list" : [ "test1", "test2" ]
  }, {
    "user_group" : "CTS view",
    "user_list" : [ "test3", "test4" ]
  } ],
  "topic_id" : "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:test"
}

Example Responses

Status code: 201

Creation succeeded.

{
  "create_time" : 1634001495876,
  "notification_id" : "cda8fd83-d08c-46f0-b914-1453a6a85c00",
  "notification_name" : "test",
  "agency_name" : "cts_admin_trust",
  "notification_type" : "smn",
  "notify_user_list" : [ {
    "user_group" : "admin",
    "user_list" : [ "test1", "test2" ]
  }, {
    "user_group" : "CTS view",
    "user_list" : [ "test3", "test4" ]
  } ],
  "operation_type" : "customized",
  "operations" : [ {
    "resource_type" : "tracker",
    "service_type" : "CTS",
    "trace_names" : [ "createTracker", "deleteTracker" ]
  }, {
    "resource_type" : "notification",
    "service_type" : "CTS",
    "trace_names" : [ "deleteNotification", "updateNotification" ]
  }, {
    "resource_type" : "pe",
    "service_type" : "AOM",
    "trace_names" : [ "deletePolicyGroup", "updatePolicyGroup", "createPolicyGroup" ]
  } ],
  "project_id" : "24edf66e79d04187acb99a463e610764",
  "status" : "enabled",
  "topic_id" : "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:test"
}

Status Codes

Status Code	Description
201	Creation succeeded.
400	The server failed to process the request.
401	The request is rejected due to authentication failure.
403	The server understood the request but refused to authorize it.
404	The server failed to find the requested resource or some key event notifications failed to be deleted.
500	The request failed to be executed or some trackers failed to be deleted.
503	The requested service is invalid. The client should not repeat the request without modifications.

Error Codes

See Error Codes.

Parent topic: Key Event Notification Management

Previous topic: Key Event Notification Management

Next topic: Modifying a Key Event Notification

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

For any further questions, feel free to contact us through the chatbot.

Chatbot