AddMessageContact - Resource Management - Alibaba Cloud Documentation Center

Adds a contact.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

Operation: the value that you can use in the Action element to specify the operation on a resource.
Access level: the access level of each operation. The levels are read, write, and list.
Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
Condition Key: the condition key that is defined by the cloud service.
Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.

Operation	Access level	Resource type	Condition key	Associated operation
resourcemanager:AddMessageContact	create	MessageContact `acs:resourcemanager::{#accountId}:messagecontact/*`	none	none

Request parameters

Parameter	Type	Required	Description	Example
Name	string	Yes	The name of the contact. The name must be unique in your resource directory. The name must be 2 to 12 characters in length and can contain only letters.	tom
EmailAddress	string	Yes	The email address of the contact. After you specify an email address, you need to call SendEmailVerificationForMessageContact to send verification information to the email address. After the verification is passed, the email address takes effect.	someone***@example.com
PhoneNumber	string	No	The mobile phone number of the contact. Specify the mobile phone number in the `<Country code>-<Mobile phone number>` format. Note Only mobile phone numbers in the `86-<Mobile phone number>` format in the Chinese mainland are supported. After you specify a mobile phone number, you need to call SendPhoneVerificationForMessageContact to send verification information to the mobile phone number. After the verification is passed, the mobile phone number takes effect.	86-139****1234
Title	string	Yes	The job title of the contact. Valid values: FinanceDirector TechnicalDirector MaintenanceDirector CEO ProjectDirector Other	TechnicalDirector
MessageTypes	array	Yes	The types of messages received by the contact.
	string	Yes	The type of the message received by the contact. Valid values: ServiceMessage FaultMessage AccountExpenses SecurityMessage ActivityMessage ProductMessage	AccountExpenses

Response parameters

Parameter	Type	Description	Example
	object	The returned result.
RequestId	string	The request ID.	2DFCE4C9-04A9-4C83-BB14-FE791275EC53
Contact	object	The information about the contact.
ContactId	string	The ID of the contact.	c-qL4HqKONzOM7****
CreateDate	string	The time when the contact was created.	2023-03-27 17:19:21

Examples

Sample success responses

JSONformat

{
  "RequestId": "2DFCE4C9-04A9-4C83-BB14-FE791275EC53",
  "Contact": {
    "ContactId": "c-qL4HqKONzOM7****",
    "CreateDate": "2023-03-27 17:19:21"
  }
}

Error codes

HTTP status code	Error code	Error message	Description
400	MissingParameter.Name	You must specify Name.	You must specify Name.
400	InvalidParameter.Name	The Name is invalid.	The value of the Name parameter is invalid. The value can contain only letters.
400	InvalidParameter.Name.Length	The Name exceeds the length limit.	The length of the value specified for the Name parameter exceeds the upper limit. The value must be 2 to 12 characters in length and can contain only letters.
400	InvalidParameter.Name.AlreadyUsed	The Name already exists. Please change to another name.	The contact name already exists in the resource directory. Use another name.
400	MissingParameter.EmailAddress	You must specify EmailAddress.	The EmailAddress parameter is not configured.
400	InvalidParameter.EmailAddress	The EmailAddress is invalid.	The value of the EmailAddress parameter is invalid.
400	MissingParameter.PhoneNumber	You must specify PhoneNumber.	The PhoneNumber parameter is not configured.
400	InvalidParameter.PhoneNumber	The PhoneNumber is invalid.	The value of the PhoneNumber parameter is invalid.
400	MissingParameter.Title	You must specify Title.	The Title parameter is not configured.
400	InvalidParameter.Title	The Title is invalid.	The value of the Title parameter is invalid.
400	MissingParameter.MessageTypes	You must specify MessageTypes.	The MessageTypes parameter is not configured.
400	InvalidParameter.MessageTypes	The MessageTypes is invalid.	The value of the MessageTypes parameter is invalid.
400	LimitExceeded.Contacts	The maximum number of contacts in a resource directory exceeds the limit.	The number of contacts exceeds the upper limit.
400	InvalidParameter.MobileCountryCode	The current site does not support the country code.	The specified country code is not supported at the current site.
400	InvalidParameter.EmailAddress.Length	The EmailAddress exceeds the length limit.	The length of the value specified for the EmailAddress parameter exceeds the upper limit.
429	ConcurrentCallNotSupported	The operation conflicts with other operations. Please try again later.	The operation conflicts with other operations. Try again later.

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation
2023-07-25	The Error code has changed	View Change Details