Binds a mobile phone number to a member of the resource account type in a resource directory for security purposes.
Operation description
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.
Debugging
Authorization information
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 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.
| xx-13900001234 |
| AccountId | string | Yes | The Alibaba Cloud account ID of the member. | 138660628348**** |
Response parameters
Examples
Sample success responses
JSONformat
{
"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. | 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 account does not pass enterprise real-name verification. Complete the verification for the account 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 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 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. | A mobile phone number is already bound to the member for security purposes. |
| 409 | CallerIdentityError | Please use the RAM user or role of the Management Account. | Only a RAM user or RAM role within the management account can be used to perform this operation. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation | ||||||
|---|---|---|---|---|---|---|---|---|
| 2023-04-27 | The Error code has changed | see changesets | ||||||
| ||||||||
| 2023-04-27 | The Error code has changed | see changesets | ||||||
|