Skip to main content
Directly download the current account’s API call details as CSV, suitable for financial reconciliation, offline analysis, or saving large volumes of records. If you only need to view a small number of details on the page, please first use the Call Record List. The query range for call records and billing summaries is the most recent 60 days; request and response bodies are separately retained for the most recent 30 days. Body expiration does not change the actual deduction, usage, or aggregate statistics of the record.

Preparation

  1. Log in to the AceDataCloud Platform.
  2. Create an account token in the Account Token Console, and immediately save it to a password manager or Secret Manager.
  3. Obtain filter IDs as needed from the Service Application List, API Credential List, or API List.
For complete token instructions, see Manage Account Tokens. Account tokens and Credentials for calling business APIs cannot be used interchangeably.

API Overview

This API synchronously streams and returns CSV, does not create an export task, and does not return JSON or a download link. Only when both the start and end times are not provided does it default to exporting records from the start of the current calendar month to the current time; when only one boundary is provided, the other boundary is not automatically filled with the current month’s boundary.

Query Parameters

The export scope is always limited to records visible to the current account as the billing entity and/or actual caller, and cross-account exports are not supported.

Request Examples

Directly save the current month’s CSV:
Export by Application, time, and status code:
Stream-save with Python and check integrity:

CSV Columns

The CSV header order is fixed as:
The quota unit is determined by the corresponding Application’s service.unit.

Determining Whether the Export Is Complete

A single export outputs up to 1,000,000 records. After the server has started returning CSV, it cannot change an intermediate error to another HTTP status, so the client must check the last line:
  • # truncated:: The row limit has been reached; export in segments using smaller time windows.
  • # error:: Streaming read was interrupted; reduce the scope and export again.
When a reconciliation program sees either marker, it must treat the file as incomplete and must not silently post it.

Errors and Retries

Next Steps