> For the complete documentation index, see [llms.txt](https://docs.coherent.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherent.global/navigation/api-call-history.md).

# API Call History

Spark stores all the API calls made to the Spark services. The *API Call History* can be used to display information about individual API calls and downloading subsets of API calls.

To access this feature, after choosing a specific service from [Folder overview](/navigation/folder-overview.md), choose the ![](/files/RmVGMBXSQh5ykxHZyA0I)*API Call History* icon from the service sidebar.

## View and filter API calls

The *API Call History* page shows the list of all the API calls made to a Spark service.

* By default, all service versions are shown by descending *Log time*.
* Additional filters can be applied to the API calls.
* *Call Purpose*, *Correlation ID*, and *Source System* are fields that can be included into the [Execute API (v3)](/spark-apis/execute-api/execute-api-v3.md#request_meta) when making a call to the Spark API. It allows the system making the call to include some identifiers that can be reviewed through the API Call History.

## Review an individual API call

### View the detailed log of the API call

Interrogate the specifics of an API call for review. In the "three-dot menu", choose *Inspect detailed log*.

The *Detailed log* will display information about the API call including the [Execute API (v3)](/spark-apis/execute-api/execute-api-v3.md#request-body) and [Execute API (v3)](/spark-apis/execute-api/execute-api-v3.md#response-body).

### Download the Excel file with inputs

Business users may want to review the specifics of an API call in Excel to review the calculation and to maintain for record keeping. A copy of the Excel file can be downloaded in the "three-dot menu", choose *Download as Excel*.

1. Spark input ranges such as `Xinput` will be populated with the fields from the API request. If a field is not provided and the default is used, the default will be populated instead of the API call input.
2. Spark output ranges such as `Xoutput` will not be populated with the fields from the API response. This is because the original formulas should not be overwritten.

There are multiple options for *Download as Excel file*:

* *Download as Excel file* users our latest technology which is faster and has better support for dynamic array functions such as [Using CS.SPARK\_XCALL() UDF](/build-spark-services/call-spark-service-apis/using-cs.spark_xcall-udf.md).
* *Download as Excel file (Legacy)* uses our previous implementation. The resulting Excel file includes a cover worksheet to describe the originating Spark service. There may be some inconsistencies compared to the current implementation.

### Run in API Tester

The inputs from the particular API call can be sent to the [API Tester](/navigation/api-tester.md) to make it easier to repeat an API call again.

## Download the API Call History

A flat file containing the API Call History can be useful for regression testing and analysis.

1. [#view-and-filter-api-calls](#view-and-filter-api-calls "mention") to identify the relevant API calls.
2. A further subset of the API calls can be selected using the checkboxes.
3. Click the **Download all API calls** button.
4. There will be different download options available.
5. The resulting file will include the exact inputs/outputs that from the filtered API calls.
   * The downloaded results file can be used as a testbed in the Testing Center, see [Testing Center](/navigation/testing-center.md#create-new-testbed).
