Creates a financial relationship.
Operation description
For more information about a financial relationship, see Usage notes on the trusteeship.
If enterprise names used by the management account and a member for real-name verification are the same, you do not need to call an API operation for confirmation. Otherwise, you must call the ConfirmRelation operation for confirmation.
Debugging
Authorization information
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RelationType | string | Yes | The type of the financial relationship. Set the value to enterprise_group. | enterprise_group |
| ParentUserId | long | Yes | The ID of the Alibaba Cloud account that is used as the management account. | 1738376485192612 |
| ChildNick | string | Yes | The display name of the member. This helps clarify the scenario in which the account is used. | xxx project |
| ChildUserId | long | Yes | The ID of the Alibaba Cloud account that is used as the member. | 1512996702208737 |
| RequestId | string | Yes | The unique ID of the request. The ID is used to mark a request and troubleshoot a problem. | 32324242444 |
| PermissionCodes | array | No | The permissions that can be granted to the member. Valid values:
The params[PermissionCodes, RoleCodes] can not be null at the same time. | |
| string | No | The permission that is granted. | SYNCHRONIZE_FINANCE_IDENTITY | |
| RoleCodes | array | No | The roles that can be assigned to the member. Set the value to trusteeship. | |
| string | No | The role that is assigned to the member in a trusteeship. The params[PermissionCodes, RoleCodes] can not be null at the same time. | trusteeship |
Response parameters
Examples
Sample success responses
JSONformat
{
"Code": 200,
"Message": "Message returned\n",
"RequestId": "Request ID\n",
"Success": true,
"Data": {
"HostId": "HostId",
"RelationId": 0
}
}Error codes
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2021-12-14 | The response structure of the API has changed | View Change Details |
