Help Center/ Workspace/ API Reference/ Workspace APIs/ App Center/ Assigning Application Authorization

Updated on 2026-02-10 GMT+08:00

View PDF

Assigning Application Authorization

Function

Assigns application authorization.

Debugging

You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.

Authorization Information

Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.

If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.

If you are using identity policy-based authorization, the following identity policy-based permissions are required.

Action	Access Level	Resource Type (*: required)	Condition Key	Alias	Dependencies
workspace:appcenter:batchUpdateAppAuthorizations	Write	-	-	-	-

URI

POST /v1/{project_id}/app-center/apps/{app_id}/actions/assign-authorizations

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID.
app_id	Yes	String	Application ID.

Request Parameters

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
authorization_type	Yes	String	ALL_USER: all users ASSIGN_USER: authorized users
users	No	Array of AccountInfo objects	New authorized users. 0 to 100 users are allowed for each request.
del_users	No	Array of AccountInfo objects	Users whose authorization is canceled. 0 to 100 users are allowed for each request.

**Table 3** AccountInfo
Parameter	Mandatory	Type	Description
account	Yes	String	Account. The account must be in the format of account (group).
domain	No	String	Domain name (mandatory for user groups. If this parameter is left blank, the default value local.com is used.)
account_type	Yes	String	User type.
platform_type	No	String	Platform type: AD: AD domain LOCAL: LiteAS

Response Parameters

Status code: 200

Response to a successful request.

Status code: 400

**Table 4** Response body parameters
Parameter	Type	Description
error_code	String	Error code, which is returned upon failure.
error_msg	String	Error description.

Status code: 401

**Table 5** Response body parameters
Parameter	Type	Description
error_code	String	Error code, which is returned upon failure.
error_msg	String	Error description.

Status code: 403

**Table 6** Response body parameters
Parameter	Type	Description
error_code	String	Error code, which is returned upon failure.
error_msg	String	Error description.

Status code: 404

**Table 7** Response body parameters
Parameter	Type	Description
error_code	String	Error code, which is returned upon failure.
error_msg	String	Error description.

Status code: 405

**Table 8** Response body parameters
Parameter	Type	Description
error_code	String	Error code, which is returned upon failure.
error_msg	String	Error description.

Status code: 500

**Table 9** Response body parameters
Parameter	Type	Description
error_code	String	Error code, which is returned upon failure.
error_msg	String	Error description.

Status code: 503

**Table 10** Response body parameters
Parameter	Type	Description
error_code	String	Error code, which is returned upon failure.
error_msg	String	Error description.

Example Requests

{
  "authorization_type" : "ALL_USER",
  "users" : [ {
    "account" : "zhangsan******@test.com",
    "domain" : "siv.**.huawei.com",
    "account_type" : "SIMPLE",
    "platform_type" : "AD"
  } ],
  "del_users" : [ {
    "account" : "zhangsan******@test.com",
    "domain" : "siv.**.huawei.com",
    "account_type" : "SIMPLE",
    "platform_type" : "AD"
  } ]
}

Example Responses

None

Status Codes

Status Code	Description
200	Response to a successful request.
400	The request cannot be understood by the server due to malformed syntax.
401	Authentication failed.
403	No operation permissions.
404	No resources found.
405	The method specified in the request is not allowed.
500	An internal service error occurred. For details about the error code, see the error code description.
503	Service unavailable.