---
title: "Upload File"
method: POST
path: "/v1/disputes/{disputeId}/files"
tags: ["Disputes", "Internal"]
---

# Upload File

`POST /v1/disputes/{disputeId}/files`

Upload a file to a dispute as `multipart/form-data` when the `UPLOAD_FILE` capability is allowed.

The `file` part must contain raw binary data (for example PDF or image bytes). Base64-encoded file content is not supported, including when indicated via `Content-Transfer-Encoding: base64`. Omit Content-Transfer-Encoding or use `binary`.

Set an appropriate Content-Type on the file part, such as `application/pdf` or `image/png`.

## Path parameters

- `disputeId` string, required

## Headers

- `Request-Reference` string
- `Request-Idempotency-Key` string

## Response `201`

Successfully uploaded the file and linked to a dispute

- FileResponse — File resource response with HATEOAS links
  - `id` string — The unique file identifier starting with file_.
  - `name` string — Name of the file.
  - `createdAt` string, date-time — Date and time when the file was created.
  - `phase` 'PRE_DISPUTE' | 'DISPUTE' | 'PRE_ARBITRATION' | 'ARBITRATION', required — Phase when the file was added.
  - `sender` 'MERCHANT' | 'PROVIDER', required — Sender of the file.
  - `status` 'PENDING' | 'FAILED' | 'AVAILABLE' | 'SYNCED_WITH_PROVIDER' — Status of the file.
  - `_links` Links

## Other responses

- `400` — Bad Request
- `404` — Not found
- `409` — Target event could not be reset due to a concurrent update.
- `500` — Internal Server Error

---

[API](https://skmtc.net/ppro/apis/payment-charges.md) · [All operations](https://skmtc.net/ppro/apis/payment-charges/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ppro/payment-charges/revisions/112e8bb4c815/schema)