All Products
Search
Document Center

MaxCompute:GetQuotaUsage

Last Updated:Jun 16, 2025

Queries quota resource consumption information.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
odps:GetQuotaUsageget
*Quota
acs:odps:{#regionId}:{#accountId}:quotas/{#nickName}
    none
none

Request syntax

GET /api/v1/quotas/{nickname}/usage HTTP/1.1

Request parameters

ParameterTypeRequiredDescriptionExample
nicknamestringYes

The alias of the level-1 quota.

os_quota_p
tenantIdstringNo

The ID of the tenant. You can log on to the MaxCompute console, and choose Tenants > Tenant Property from the left-side navigation pane to view the tenant ID.

478403690625249
regionstringNo

The region ID.

cn-chengdu
fromlongYes

The time when the query starts. The value is the log time that is specified when log data is written.

  • The time range that is specified in this operation is a left-closed, right-open interval. The interval includes the start time specified by the from parameter, but does not include the end time specified by the to parameter. If you set the from and to parameters to the same value, the time range is invalid and an error message is returned.
  • This value is a UNIX timestamp representing the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC.
1669081045
tolongYes

The time when the query ends. The value is the log time that is specified when log data is written.

  • The time range that is specified in this operation is a left-closed, right-open interval. The interval includes the start time specified by the from parameter, but does not include the end time specified by the to parameter. If you set the from and to parameters to the same value, the time range is invalid and an error message is returned.
  • This value is a UNIX timestamp representing the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC.
1669360870
subQuotaNicknamestringNo

The alias of the level-2 quota.

ot_tunnel_quota
aggMethodstringNo

The aggregation algorithm. For a better page experience, up to 60 points can be displayed for each metric. If you select a time range longer than 1 hour, the chart uses the average value within the range (minutes of the selected time range/60) to aggregate data by default. You can change the aggregation algorithm based on your business requirements.

max
productIdstringNo

The quota type. Default value: ODPS.

  • ODPS: computing quota
  • TUNNEL: Tunnel quota
ODPS
plotTypesarrayNo

The types of the charts.

itemstringNo

The type of the chart.

When productId is set to ODPS, this parameter is optional and has the following valid values:

  • cpu: CPU resources.
  • memory: memory resources. If this parameter is not configured, both metrics are returned.

When productId is set to TUNNEL, this parameter is required and has the following valid values:

  • request: the request parallelism.
  • throughput: the throughput.
  • error: the number of error requests.
cpu
yAxisTypesarrayNo

The data metric fields.

itemstringNo

The data metric field.

You do not need to specify this parameter if the productId parameter is set to ODPS.

You can enter a project name when productId is set to TUNNEL. In this case, the returned result is the information of the project dimension.

your_project_name

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

requestIdstring

The request ID.

0b87b7a416652014358483492eea0b
httpCodeinteger

The HTTP status code.

  • 1xx: informational response. The request is received and is being processed.
  • 2xx: success. The request is successfully received, understood, and accepted by the server.
  • 3xx: redirection. The request is redirected, and further actions are required to complete the request.
  • 4xx: client error. The request contains invalid request parameters and syntaxes, or specific request conditions cannot be met.
  • 5xx: server error. The server cannot meet requirements due to other reasons.
200
errorCodestring

The error code.

OBJECT_NOT_EXIST
errorMsgstring

The error message.

This object does not exist.
dataobject

The data returned.

metricsobject

The metric results.

plotarray<object>

The information about the chart.

plotobject

The information about the chart.

titlestring

The title of the chart.

request
typestring

The type of the chart.

request
yAxisarray

The data metric field.

yAxisstring

The data metric field.

If the productId parameter is set to ODPS: CPU metric type or memory metric type

If the productId parameter is set to TUNNEL and a project name is entered: project#operation#type

project1#download#request

Examples

Sample success responses

JSONformat

{
  "requestId": "0b87b7a416652014358483492eea0b",
  "httpCode": 200,
  "errorCode": "OBJECT_NOT_EXIST",
  "errorMsg": "This object does not exist.",
  "data": {
    "metrics": {
      "test": "test",
      "test2": 1
    },
    "plot": [
      {
        "title": "request",
        "type": "request",
        "yAxis": [
          "project1#download#request"
        ]
      }
    ]
  }
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2022-08-18Add OperationView Change Details