Skip to main content
Summarize the current account’s request count and actual deducted quota by date and API, suitable for creating monthly reports, trend charts, and cost analysis. Use the Call Record List when troubleshooting item by item, and use Usage Export when complete offline details are needed. The query range for call records and billing summaries is the most recent 60 days; request and response bodies are retained separately for the most recent 30 days. Body expiration does not change the actual charge, usage, or aggregate statistics of the record.

Preparations

  1. Log in to the AceDataCloud Platform.
  2. Create an account token in the Account Token Console, and save it immediately.
  3. To narrow the scope, obtain the corresponding ID from the Service Application List, API Credential List, or API List.
For complete token instructions, see Manage Account Tokens. This API uses an Account Token, not a business Credential.

API Overview

Query Parameters

start_time / end_time can still be used as backward-compatible aliases for older clients. New integrations should consistently use created_at_from / created_at_to. A date-form created_at_to includes that calendar day, using midnight of the next day as the boundary.

Request Examples

Query daily/API aggregates for the current month in Beijing time, with model dimensions included:
Query one week’s usage for a specified Application:
Python example:

Response Example

Response Fields

The quota unit depends on the service.unit of the associated Application. If the query includes services with different units, first calculate them separately by service_id or application_id to avoid directly comparing or adding them. When the end time is not greater than the start time, the API returns a complete empty structure: items=[], total=0, apis={}, requests=0, models=[].

Error and Performance Recommendations

  • Do not enable include_models by default; enable it only when the report truly requires model breakdowns.
  • For large-range queries, prioritize separating them by service_id or application_id; this both avoids mixed units and reduces query cost.
  • Dates without calls are not automatically filled with zero; the client should fill in the date axis before charting.

Next Steps