This page queries the call records of the account itself. If you only want to view the public call statistics of an API across the entire platform, please use API Call Statistics.
Data Retention Scope
Call records and billing summaries are retained for the last 60 days; request and response bodies are retained for the last 30 days. Records from 30–60 days ago can still be queried for summaries such as trace, status, time, model, usage, and actual charges, butmetadata.request and metadata.response in the details will no longer be returned. Summaries required for model aggregation and valid result statistics are retained until the body expires. If you need to retain bodies long-term, please save them yourself when making calls.
Preparation
1. Create an Account Token
This API is a platform management API and requires an Account Token:- Log in to the AceDataCloud Platform.
- Open the Account Token Console.
- Click “Create” and immediately save the token to a password manager or Secret Manager.
platform.acedata.cloud/api/v1/**; API credentials (Credential) are used to call api.acedata.cloud/** business APIs, and the two cannot be used interchangeably.
2. Prepare Filter IDs (Optional)
You can view records that the current account is authorized to view without passing filter conditions. When you need to narrow the scope:application_id: obtain it from the Service Application List;credential_id: obtain it from the API Credential List;api_id: obtain it from the API List;service_id: obtain it from the Service List.
user_id; if explicitly passed, it must match the current account, otherwise 403 is returned. Administrators can use this parameter to filter across accounts.
API Overview
Query Scope
Query Parameters
When the request time is earlier than the last 60 days, the API returns a
400 field validation error, indicating that complete call details are retained for only 60 days.
Request Examples
Query the latest 100 records:Response Example
Key Fields
The quota unit is determined by the corresponding Application’s
service.unit and should not be assumed to be US dollars by default.
Errors and Retries
For the same set of query parameters, at most one in-flight request is maintained. For large-range queries, prioritize using a one-day or smaller window, and do not stack identical requests at fixed intervals.
Next Steps
- Aggregate Usage: View usage summarized by date and API.
- Export Usage: Download large amounts of details directly as CSV.
- View Proxy Usage Records: Query records for Proxy-type services.
- View Service Application Details: Verify the balance and quota unit.
- Rotate API Credentials: Replace credentials immediately if they are suspected of being compromised.

