Deleting Tags from Resource Shares

This API is used to delete the specified tags from resource shares.

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

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
ram:resourceShares:untag	Tagging	resourceShare *	g:ResourceTag/<tag-key>	-	-
ram:resourceShares:untag	Tagging	-	g:RequestTag/<tag-key> g:TagKeys	-	-

POST /v1/resource-shares/{resource_share_id}/tags/delete

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
resource_share_id	Yes	String	ID of the resource share.

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Security-Token	No	String	Security token (session token) of your temporary security credentials. If a temporary security credential is used, this header is required.

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
tags	Yes	Array of Untag objects	List of one or more tag key-value pairs. The tag key cannot be left blank or be an empty string. The tag value must be specified and can be an empty string.

**Table 4** Untag
Parameter	Mandatory	Type	Description
key	Yes	String	Identifier or name of the tag key.
value	No	String	Value of the tag key. You can set the tag value to an empty string but not to null.

Status code: 200

Request succeeded.

None

Deleting tags from a resource share

POST /v1/resource-shares/{resource_share_id}/tags/delete

{
  "tags" : [ {
    "key" : "string",
    "value" : "string"
  } ]
}

None

Status Code	Description
200	Request succeeded.

Parent topic: Tag Management

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

For any further questions, feel free to contact us through the chatbot.