All Products
Search
Document Center

Edge Security Acceleration:DescribeDcdnUserBillHistory

Last Updated:Aug 21, 2025

You can call DescribeDcdnUserBillHistory to query historical bills for a period of up to one month.

Operation description

Note

The call frequency for a single user is limited to 100 calls per second.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

dcdn:DescribeDcdnUserBillHistory

get

*All Resource

*

None None

Request parameters

Parameter

Type

Required

Description

Example

StartTime

string

Yes

The beginning of the time range to query. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.

The minimum data granularity is 5 minutes.

2018-09-30T16:00:00Z

EndTime

string

Yes

The end of the time range to query. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.

The end time must be later than the start time.

2018-10-31T16:00:00Z

Response elements

Parameter

Type

Description

Example

object

RequestId

string

The request ID.

ED61C6C3-8241-4187-AAA7-5157AE175CEC

BillHistoryData

object

BillHistoryDataItem

array<object>

The historical billing data.

object

Dimension

string

The dimension.

vas

BillType

string

The billing pattern.

month_4th_day_bandwidth

BillTime

string

The start time of the billing cycle.

2018-09-30T17:00:00Z

BillingData

object

BillingDataItem

array<object>

The billing data.

object

Flow

number

The traffic. Unit: bytes.

2456

Bandwidth

number

The bandwidth. Unit: Bps.

4839

Count

number

The count.

205624

CdnRegion

string

The billing region. Valid values: CN, OverSeas, AP1, AP2, AP3, NA, SA, EU, and MEAA.

AP1

ChargeType

string

The billing type. Valid values: StaticHttp, DynamicHttp, and DynamicHttps.

DynamicHttp

Examples

Success response

JSON format

{
  "RequestId": "ED61C6C3-8241-4187-AAA7-5157AE175CEC",
  "BillHistoryData": {
    "BillHistoryDataItem": [
      {
        "Dimension": "vas",
        "BillType": "month_4th_day_bandwidth",
        "BillTime": "2018-09-30T17:00:00Z",
        "BillingData": {
          "BillingDataItem": [
            {
              "Flow": 2456,
              "Bandwidth": 4839,
              "Count": 205624,
              "CdnRegion": "AP1",
              "ChargeType": "DynamicHttp"
            }
          ]
        }
      }
    ]
  }
}

Error codes

HTTP status code

Error code

Error message

Description

400 InvalidParameters The specified parameters are invalid. A parameter is set to an invalid value.
400 InvalidStartTime.Malformed The specified StartTime parameter is invalid. The format of the specified start time is invalid. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.
400 InvalidEndTime.Malformed The specified EndTime is invalid. The format of the specified end time is invalid. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.
400 InvalidEndTime.Mismatch The specified EndTime is earlier than the StartTime. The end time is earlier than the start time.
400 InvalidTimeSpan The time span exceeds the limit. The time span exceeds the limit. Configure a valid time span as described in API documentation.
400 InvalidTime.Malformed Specified StartTime or EndTime is malformed. The format of the specified start time or end time is invalid. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.