Querying the Quotas of a Project
Function
This API is used to query the quotas of a specified project.
The API can be called using both the global endpoint and region-specific endpoints.
URI
GET /v3.0/OS-QUOTA/projects/{project_id}
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
ID of the project to be queried. For details about how to obtain the project ID, see Obtaining Account, IAM User, Group, Project, Region, and Agency Information. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
A token with Security Administrator permissions or an IAM user token. (No special permissions are required, but the scope of the token must be the project specified in the URL.) |
Response Parameters
Parameter |
Type |
Description |
---|---|---|
object |
Quota information of the account. |
Example Request
Request for querying the project quota
GET https://iam.myhuaweicloud.eu/v3.0/OS-QUOTA/projects/{project_id}
Example Response
Status code: 200
The request is successful.
{ "quotas" : { "resources" : [ { "max" : 50, "min" : 0, "quota" : 10, "type" : "project", "used" : 4 } ] } }
Status code: 403
Access denied.
- Example 1
{ "error_msg" : "You are not authorized to perform the requested action.", "error_code" : "IAM.0002" }
- Example 2
{ "error_msg" : "Policy doesn't allow %(actions)s to be performed.", "error_code" : "IAM.0003" }
Status code: 404
The requested resource cannot be found.
{ "error_msg" : "Could not find %(target)s: %(target_id)s.", "error_code" : "IAM.0004" }
Status code: 500
Internal server error.
{ "error_msg" : "An unexpected error prevented the server from fulfilling your request.", "error_code" : "IAM.0006" }
Status Codes
Status Code |
Description |
---|---|
200 |
The request is successful. |
401 |
Authentication failed. |
403 |
Access denied. |
404 |
The requested resource cannot be found. |
500 |
Internal server error. |
Error Codes
For details, see Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.