Use BindSecureMobilePhone to bind a secure mobile phone to a member account - Resource Management - Alibaba Cloud - Resource Management

Operation description

This operation only binds a mobile phone number to a resource account member. It cannot change an already bound mobile phone number.

To ensure that management operations are traceable, call this operation by using a RAM user or RAM role that has the AliyunResourceDirectoryFullAccess policy attached within your management account.

The following example shows how to bind a security mobile phone number to the member 138660628348****.

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

resourcemanager:BindSecureMobilePhone

update

*Account

acs:resourcemanager:*:{#accountId}:account/{#ResourceDirectoryPath}

None

Request parameters

Parameter	Type	Required	Description	Example
VerificationCode	string	Yes	The verification code. You can call the SendVerificationCodeForBindSecureMobilePhone operation to obtain the verification code.	123456
SecureMobilePhone	string	Yes	The mobile phone number to bind to the member for security purposes. This number must match the one specified when you called the SendVerificationCodeForBindSecureMobilePhone operation to obtain a verification code. Specify the mobile phone number in the <Country code>-<Mobile phone number> format. Note Mobile phone numbers in the `86-<Mobile phone number>` format in the Chinese mainland are not supported.	xx-13900001234
AccountId	string	Yes	The Alibaba Cloud account ID of the member.	138660628348****

For more information about common request parameters, see Common parameters.

Response elements

Element	Type	Description	Example
	object
RequestId	string	The request ID.	0217AFEB-5318-56D4-B167-1933D83EDF3F

Examples

Success response

JSON format

{
  "RequestId": "0217AFEB-5318-56D4-B167-1933D83EDF3F"
}

Error codes

HTTP status code	Error code	Error message	Description
400	NotSupport.Site.Action	Site does not allow current action.	Site does not allow current action.
409	NotSupport.AccountInAnotherResourceDirectory	The specified account is an Alibaba Cloud account or already exists in another resource directory.
409	Invalid.EnterpriseName	You must specify the enterprise name.	You must specify the enterprise name.
409	EnterpriseRealNameVerificationError	The specified account does not pass enterprise real-name verification. We recommend you first complete enterprise real-name verification for the account.	The specified account does not pass enterprise real-name verification. We recommend you first complete enterprise real-name verification for the account.
409	EntityAlreadyExists.ResourceDirectory	The resource directory for the account is already enabled. We recommend that you do not enable the resource directory again.	The resource directory for the account is already enabled. We recommend that you do not enable the resource directory again.
409	Invalid.VerificationCode	The verification code is invalid.	The verification code is invalid.
409	AccountTypeMismatch	The type or status of the member account cannot satisfy the current operation.	The type or status of the member account cannot satisfy the current operation.
409	AccountSecureMobileAlreadyExists	The secure mobile number of the member already exists.	The secure mobile number of the member already exists.
409	CallerIdentityError	Please use the RAM user or role of the Management Account.	Use the RAM user or role of the management account to perform this operation.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.