Batch Deleting Resource Tags
Function
This API is used to delete tags from a specified instance in batches.
- This API is idempotent, meaning that if the tag to be deleted does not exist, the deletion is successful.
- A maximum of 20 tags can be deleted in a batch.
- Character set validation is not performed when deleting tags.
- The tags structure cannot be missing during deletion, and the key field cannot be empty or a null string.
URI
POST /v3/{project_id}/{resource_type}/{resource_id}/tags/delete
| Parameter | Mandatory | Type | Description | 
|---|---|---|---|
| project_id | Yes | String | Project ID, which is used for resource isolation. For details about how to obtain a project ID, see Obtaining a Project ID. | 
| resource_type | Yes | String | Resource type. The options are: 
 | 
| resource_id | Yes | String | Resource ID. Minimum length: 1 character Maximum length: 1,000 characters 
        Obtain it as follows:
         
 | 
Request Parameters
| Parameter | Mandatory | Type | Description | 
|---|---|---|---|
| tags | Yes | Array of tags objects | Tag list. For details, see Table 3. 
 | 
| Parameter | Mandatory | Type | Description | 
|---|---|---|---|
| key | Yes | String | Tag key. A tag key can contain a maximum of 128 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed, but the value cannot start or end with a space or start with _sys_. | 
| value | Yes | String | Tag value. A tag value can contain a maximum of 255 characters. Only letters, digits, spaces, and special characters (_.:+-@) are allowed. | 
Response Parameters
None
Example Request
{
    "tags":[
        {
            "key":"key1"
        },
        {
            "key":"key2",
            "value":"value2"
        }
    ]
}
 Example Response
None
Status Codes
| Status Code | Description | 
|---|---|
| 204 | The modification is successful. | 
| 400 | Request error. | 
| 500 | Internal server error. | 
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
 
    