Queries the numbers of resources on which the current account has access permissions.
Debugging
Authorization information
There is currently no authorization information disclosed in the API.
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
GroupByKey | string | No | The dimension by which resources are queried. Valid values:
| ResourceType |
Filter | object [] | No | The filter conditions. | |
Key | string | No | The key of the filter condition. For more information, see | RegionId |
Value | array | No | The values of the filter condition. | |
string | No | A value of the filter condition. | cn-shanghai | |
MatchType | string | No | The matching mode. The value Equals indicates an equal match. | Equals |
Supported filter parameters
Parameter | Description | Supported matching mode |
---|---|---|
ResourceType | The resource type. | Equals |
RegionId | The region ID. | Equals |
ResourceId | The resource ID. | Equals and Prefix |
ResourceGroupId | The resource group ID. | Equals, Exists, and NotExists |
ResourceName | The resource name. | Equals and Contains |
Tag | The key-value pair. The key-value pair must be in the { "key": $key, "value": $value } JSON format. You must specify at least one of key and value. For example, if you want to query the tag key foo and tag value bar , set this parameter to { "key": "foo", "value": "bar" } . If you want to query only the tag key foo , set this parameter to { "key": "foo" } . | Contains, NotContains, and NotExists |
VpcId | The VPC ID. | Equals |
VSwitchId | The vSwitch ID. | Equals |
Response parameters
Examples
Sample success responses
JSON
format
{
"GroupByKey": "ResourceType",
"RequestId": "6D98D9B0-318D-56A4-910C-93B5F945AF2B",
"Filters": [
{
"Key": "RegionId",
"Values": [
"cn-shanghai"
]
}
],
"ResourceCounts": [
{
"GroupName": "ACS::ECS::NetworkInterface",
"Count": 2
}
]
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation | ||
---|---|---|---|---|
2023-08-22 | The internal configuration of the API is changed, but the call is not affected | see changesets | ||
|