Binds a mobile phone number to a member of the resource account type in a resource directory for security purposes.

Usage notes

You can call this API operation only to bind a mobile phone number to a member of the resource account type. You cannot call this API operation to change the mobile phone number that is bound to a member of the resource account type.

To ensure that the system can record the operators of management operations, you must use a RAM user or RAM role to which the AliyunResourceDirectoryFullAccess policy is attached within the management account of your resource directory to call this API operation.

This topic provides an example on how to call the API operation to bind a mobile phone number to the member 138660628348**** for security purposes.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes BindSecureMobilePhone

The operation that you want to perform. Set the value to BindSecureMobilePhone.

VerificationCode String Yes 123456

The verification code.

You can call the SendVerificationCodeForBindSecureMobilePhone operation to obtain the verification code.

SecureMobilePhone String Yes xx-13900001234

The mobile phone number that you want to bind to the member for security purposes.

The mobile phone number you specify must be the same as the mobile phone number that you specify when you call 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.
AccountId String Yes 138660628348****

The Alibaba Cloud account ID of the member.

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

Response parameters

Parameter Type Example Description
RequestId String 0217AFEB-5318-56D4-B167-1933D83EDF3F

The request ID.

Examples

Sample requests

http(s)://[Endpoint]/?Action=BindSecureMobilePhone
&VerificationCode=123456
&SecureMobilePhone=xx-13900001234
&AccountId=138660628348****
&<Common request parameters>

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<BindSecureMobilePhoneResponse>
    <RequestId>0217AFEB-5318-56D4-B167-1933D83EDF3F</RequestId>
</BindSecureMobilePhoneResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "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. The error message returned because the operation is not supported at the current site.
409 Invalid.EnterpriseName You must specify the enterprise name. The error message returned because no enterprise name is specified for the account. Specify an enterprise name for the account.
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 error message returned because the account does not pass enterprise real-name verification. Complete enterprise real-name verification first.
409 EntityAlreadyExists.ResourceDirectory The resource directory for the account is already enabled. We recommend that you do not enable the resource directory again. The error message returned because the account has been used to enable a resource directory. Do not use the account to enable a resource directory again.
409 Invalid.VerificationCode The verification code is invalid. The error message returned because the verification code is invalid.
409 AccountTypeMismatch The type or status of the member account cannot satisfy the current operation. The error message returned because the type or status of the member does not meet the requirements for the current operation.
409 AccountSecureMobileAlreadyExists The secure mobile number of the member already exists. The error message returned because a mobile phone number has been bound to the member for security purposes.
409 CallerIdentityError Please use the RAM user or role of the Management Account. The error message returned because only a RAM user or RAM role within the management account of the resource directory can be used to call this operation.

For a list of error codes, see Service error codes.