UpdateAlertDestination - Alibaba Cloud Linux - Alibaba Cloud Documentation Center

Updates an alert contact.

Operation description

、

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

sysom:UpdateAlertDestination

update

*All Resource

*

None

Request syntax

PUT /api/v1/alertPusher/alert/updateDestination HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
body	object	No	The HTTP request body.
app_id	string	No
app_secret	string	No
group_id	array	No
	string	No
id	string	No	The ID of the alert contact.	1
imbot	boolean	No
name	string	No	The name of the alert contact.	name1
params	object	No	The configuration parameters.
email	string	No	The email address.	xxx@email.com
phone	string	No	The phone number.	1xxx
sec	string	No	The chatbot secret key.	SECxxx
webhook	string	No	The webhook URL.	https://oapi.dingtalk.com/robot/send?access_token=xxx
source	string	No	The configuration source.	console
target	string	No	The alert push target. Currently, only DingTalk contacts are supported.	dingtalk

Response elements

Element	Type	Description	Example
	object	Schema of Response
code	string	The status code. If `code == Success`, the authorization is successful. Other status codes indicate authorization failed. Check the `message` field for the detailed fault information.	SysomOpenAPI.InvalidParameter
data	any	The response result.	{ "webhook":"", "sec":"" }
message	string	The error message. If `code == Success`, this field is empty. Otherwise, this field contains the request error information.	Success
requestId	string	The request ID.	2D693121-C925-5154-8DF6-C09A8B369822

Examples

Success response

JSON format

{
  "code": "SysomOpenAPI.InvalidParameter",
  "data": "{\n\"webhook\":\"\",\n\"sec\":\"\"\n}",
  "message": "\nSuccess",
  "requestId": "2D693121-C925-5154-8DF6-C09A8B369822\n"
}

Error codes

HTTP status code	Error code	Error message	Description
400	Sysom.ServerError	Server error, please correct the code according to the error message. %s.	Server error, please correct the code according to the error message

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.