All Products
Search
Document Center

Auto Scaling:ListTagKeys

Last Updated:May 07, 2024

Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter

Type

Required

Example

Description

Action

String

Yes

ListTagKeys

The operation that you want to perform. Set the value to ListTagKeys.

RegionId

String

Yes

cn-hangzhou

The region ID of the Auto Scaling resources.

ResourceType

String

Yes

scalinggroup

The type of the Auto Scaling resources. Set the value to scalinggroup. This means the tag key you want to query is added to a scaling group.

NextToken

String

No

caeba0bbb2be03f84eb48b699f0a****

The pagination token that is used in the next request to retrieve a new page of results. If NextToken is empty, no next page exists.

PageSize

Integer

No

10

The number of entries per page. Maximum value: 50.

Default value: 10.

Response parameters

Parameter

Type

Example

Description

NextToken

String

caeba0bbb2be03f84eb48b699f0a****

A pagination token. It can be used in the next request to retrieve a new page of results.If NextToken is empty, no next page exists.

RequestId

String

DC09A6AA-2713-4E10-A2E9-E6C5C43A****

The request ID.

PageSize

Integer

10

The number of entries per page.

Keys

Array of String

ESS

The information about the tag keys.

Examples

Sample requests

http(s)://ess.aliyuncs.com/?Action=ListTagKeys
&RegionId=cn-hangzhou
&ResourceType=scalinggroup
&NextToken=caeba0bbb2be03f84eb48b699f0a****
&PageSize=10
&<Common request parameters>

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<ListTagKeysResponse>
    <NextToken>caeba0bbb2be03f84eb48b699f0a****</NextToken>
    <RequestId>DC09A6AA-2713-4E10-A2E9-E6C5C43A8842</RequestId>
    <PageSize>10</PageSize>
    <Keys>ESS</Keys>
</ListTagKeysResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "NextToken" : "caeba0bbb2be03f84eb48b699f0a****",
  "RequestId" : "DC09A6AA-2713-4E10-A2E9-E6C5C43A8842",
  "PageSize" : 10,
  "Keys" : [ "ESS" ]
}

Error codes

For a list of error codes, see Service error codes.

HTTP status code

Error code

Error message

Description

400

InvalidResourceType.NotFound

The ResourceType provided does not exist in our records.

The value of ResourceType is invalid.