# GET /api/transactions/batch-file/{id}/export-results

Exports batch processing results as a CSV file.

Only available for batches with status `Completed` or `Failed`.
The exported CSV includes per-line results: transaction type, amount,
status, result code, and any error messages.

**Operation ID:** `GET_api_transactions_batch-file_id_export-results`

## Authorization

No permission required.

## Parameters

| Name | In | Required | Type | Description |
| --- | --- | --- | --- | --- |
| id | path | yes | string(uuid) | The batch file ID. |
| suppressNulls | query | no | boolean | If true, omit properties with null values. |

## Responses

### 200

The results CSV file.

**Content type:** `text/csv`

Schema type: `string(binary)`

### 400

The batch file has not finished processing yet.

### 404

No batch file exists with the specified ID.

### 403

Forbidden

**Content type:** `text/csv`

Schema: `WinkPGHttpRemoteServiceErrorResponse`

### 401

Unauthorized

**Content type:** `text/csv`

Schema: `WinkPGHttpRemoteServiceErrorResponse`

### 501

Not Implemented

**Content type:** `text/csv`

Schema: `WinkPGHttpRemoteServiceErrorResponse`

### 500

Internal Server Error

**Content type:** `text/csv`

Schema: `WinkPGHttpRemoteServiceErrorResponse`

### default

The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. See the error-code reference in this document's description for the values `error.code` can take.

**Content type:** `application/json`

Schema: `WinkPGHttpRemoteServiceErrorResponse`

## See also

- [All documentation](https://docs.winkpg.io/llms.txt): the machine-readable index of every public page on this site.