---
title: "Upload evidence"
method: POST
path: "/v1/disputes/{dispute_token}/evidences"
tags: ["Chargeback"]
---

# Upload evidence

`POST /v1/disputes/{dispute_token}/evidences`

Use this endpoint to upload evidence for a chargeback request. It will return a URL to upload your documents to. The URL will expire in 30 minutes.

Uploaded documents must either be a `jpg`, `png` or `pdf` file, and each must be less than 5 GiB.

## Path parameters

- `dispute_token` string, uuid, required

## Request body

- object
  - `filename` string — Filename of the evidence.

## Response `201`

OK

- DisputeEvidence — Dispute evidence.
  - `created` string, date-time, required — Timestamp of when dispute evidence was created.
  - `dispute_token` string, uuid, required — Dispute token evidence is attached to.
  - `download_url` string — URL to download evidence. Only shown when `upload_status` is `UPLOADED`.
  - `filename` string — File name of evidence. Recommended to give the dispute evidence a human-readable identifier.
  - `token` string, uuid, required — Globally unique identifier.
  - `upload_status` 'DELETED' | 'ERROR' | 'PENDING' | 'REJECTED' | 'UPLOADED', required — 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` string — URL to upload evidence. Only shown when `upload_status` is `PENDING`.

## Other responses

- `400` — A parameter in the query given in the request does not match the valid queries for the endpoint.
- `401` — | | | |---|---| | User has not been authenticated | Invalid or missing API key | | API key is not active | The API key used is no longer active | | Could not find API key | The API key provided is not associated with any user | | Please provide API key in Authorization header | The Authorization header is not in the request | | Please provide API key in the form Authorization: [api-key] | The Authorization header is not formatted properly | | Insufficient privileges. Issuing API key required | Write access requires an Issuing API key. Reach out at [lithic.com/contact](https://lithic.com/contact) | | Insufficient privileges to create virtual cards. | Creating virtual cards requires an additional privilege | Reach out at [lithic.com/contact](https://lithic.com/contact) |
- `404` — The specified resource was not found.
- `429` — Client has exceeded the number of allowed requests in a given time period. | | | |---|---| | Rate limited, too many requests per second | User has exceeded their per second rate limit | | Rate limited, reached daily limit | User has exceeded their daily rate limit | | Rate limited, too many keys tried | One IP has queried too many different API keys |

---

[API](https://skmtc.net/lithic-com/apis/lithic-developer-api.md) · [All operations](https://skmtc.net/lithic-com/apis/lithic-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lithic-com/lithic-developer-api/revisions/53ab5d4e2adb/schema)