# Dispute Evidence Object

## Properties

### `evidence_token`
- **Type**: `uuid`
- **Required**: Yes

### `dispute_token`
- **Type**: `uuid`
- **Required**: Yes

### `created`
- **Type**: `date-time`
- **Required**: Yes  
  Timestamp of when dispute evidence was created.

### `download_url`
- **Type**: `string`  
  URL to download evidence. Only shown when `upload_status` is `UPLOADED`.

### `filename`
- **Type**: `string`  
  File name of evidence. Recommended to give the dispute evidence a human-readable identifier.

### `token`
- **Type**: `uuid`
- **Required**: Yes  
  Globally unique identifier.

### `upload_status`
- **Type**: `string`
- **Required**: Yes  
  Enum with upload status types:
  - `DELETED` - Evidence was deleted.
  - `ERROR` - Evidence upload failed.
  - `PENDING` - Evidence is pending upload.
  - `REJECTED` - Evidence was rejected.
  - `UPLOADED` - Evidence was uploaded.

### `upload_url`
- **Type**: `string`  
  URL to upload evidence. Only shown when `upload_status` is `PENDING`.

## Response Codes

### `200 OK`
- Object: Dispute evidence.

### `400 Bad Request`
- A parameter in the query given in the request does not match the valid queries for the endpoint.

### `401 Unauthorized`
- User has not been authenticated.
- Invalid or missing API key.
- API key is not active.
- Could not find the API key.
- Insufficient privileges.

### `404 Not Found`
- The specified resource was not found.

### `429 Too Many Requests`
- Client has exceeded the number of allowed requests in a given time period.

## Example Request
```shell
curl --request DELETE \
     --url https://sandbox.lithic.com/v1/disputes/dispute_token/evidences/evidence_token \
     --header 'accept: application/json'
```

## Example Response
```json
{
  "created": "2026-07-18T00:25:22.116Z",
  "dispute_token": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "download_url": "string",
  "filename": "string",
  "token": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "upload_status": "DELETED",
  "upload_url": "string"
}
```