Preparations
- Log in to the AceDataCloud Platform.
- Create an account token in the Account Token Console, and save it immediately.
- To narrow the scope, obtain the corresponding ID from the Service Application List, API Credential List, or API List.
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: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_modelsby default; enable it only when the report truly requires model breakdowns. - For large-range queries, prioritize separating them by
service_idorapplication_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
- View usage records: Locate the details that make up the aggregated results.
- Export usage volume: Download the complete CSV details.
- View service application details: Confirm the balance and units.

