BindSecureMobilePhone - Bind secure mobile phone to resource account member - Resource Management

Operation description

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

To ensure that the system records the operator, call this operation by using a RAM user or RAM role with the AliyunResourceDirectoryFullAccess policy attached within the management account.

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

No authorization for this operation. If you encounter issues with this operation, contact technical support.

Request parameters

Parameter	Type	Required	Description	Example
VerificationCode	string	Yes	The verification code. Obtain the verification code by calling SendVerificationCodeForBindSecureMobilePhone.	123456
SecureMobilePhone	string	Yes	The mobile phone number to bind to the member for security purposes. This number must match the one specified when calling SendVerificationCodeForBindSecureMobilePhone. Specify the mobile phone number in the <Country code>-<Mobile phone number> format. Note The `86-<Mobile phone number>` format (Chinese mainland) is not supported.	xx-13900001234
AccountId	string	Yes	The Alibaba Cloud account ID of the member.	138660628348****

Response elements

Element	Type	Description	Example
	object	The response.
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
400	NotSupport.Site.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.
409	EnterpriseRealNameVerificationError	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.
409	Invalid.VerificationCode	The verification code is invalid.
409	AccountTypeMismatch	The type or status of the member account cannot satisfy the current operation.
409	AccountSecureMobileAlreadyExists	The secure mobile number of the member already exists.
409	CallerIdentityError	Please use the RAM user or role of the Management Account.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.