Querying the Tags of All Listeners

This API is used to query the tags of all listeners in a project.

For details, see Calling APIs.

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, no identity policy-based permission required for calling this API.

GET /v3/{project_id}/listeners/tags

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Definition: Specifies the project ID. For details about how to obtain a project ID, see Obtaining a Project ID. Constraints: N/A Range: The value can contain a maximum of 32 characters, including digits and lowercase letters. Default value: N/A

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	Definition: Specifies the token used for IAM authentication. Constraints: N/A Range: N/A Default value: N/A

Status code: 200

**Table 3** Response body parameters
Parameter	Type	Description
tags	Array of ListTag objects	Definition: Specifies the tag list.

**Table 4** ListTag
Parameter	Type	Description
key	String	Definition: Specifies the tag key. Range: A tag key can contain a maximum of 36 Unicode characters.
values	Array of strings	Definition: Specifies the tag values. Range: Each value can contain a maximum of 43 Unicode characters and can be an empty string.

GET https://{ELB_Endpoint}/v3/6a0de1c3-7d74-4f4a-b75e-e57135bd2b97/listeners/tags

Status code: 200

Successful request.

{
  "tags" : [ {
    "values" : [ "value1", "value2" ],
    "key" : "key1"
  }, {
    "values" : [ "value1", "value2" ],
    "key" : "key2"
  } ]
}

Status Code	Description
200	Successful request.

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.