All Products
Search
Document Center

MaxCompute:GetComputeQuotaSchedule

Last Updated:Jun 19, 2025
This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Displays the time-specific configuration of compute quota.

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:GetQuotaScheduleget
*Quota
acs:odps:{#regionId}:{#accountId}:quotas/{#NickName}
    none
none

Request syntax

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

Request parameters

ParameterTypeRequiredDescriptionExample
nicknamestringYes

The nickname of level-1 compute quota.

os_ComputeQuota_p
displayTimezonestringNo

Display time zone.

UTC+8

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

requestIdstring

The request ID.

B42CA730-8187-50F1-9FE0-6733297036DB
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 or 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.

QUOTA_UNKNOWN_NICKNAME
errorMsgstring

The error message.

Cannot found quota **
dataarray<object>

The data returned.

dataobject
idstring

The ID of the quota plan.

89b54db44d384f26964951ea457f64a5
typestring

The type of the quota plan.

daily
planstring

The name of the quota plan.

planA
conditionobject

The value of effective condition.

atstring

The start time when the quota plan takes effect.

09:00
timezonestring

The time zone property.

UTC+8

Examples

Sample success responses

JSONformat

{
  "requestId": "B42CA730-8187-50F1-9FE0-6733297036DB",
  "httpCode": 200,
  "errorCode": "QUOTA_UNKNOWN_NICKNAME",
  "errorMsg": "Cannot found quota **",
  "data": [
    {
      "id": "89b54db44d384f26964951ea457f64a5",
      "type": "daily",
      "plan": "planA",
      "condition": {
        "at": "09:00"
      },
      "timezone": "UTC+8"
    }
  ]
}

Error codes

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