---
title: "Upload a dispute evidence file"
method: POST
path: "/files"
---

# Upload a dispute evidence file

`POST /files`

Uploads one file for later dispute evidence submission. The upload records the supplied case reference without calling the dispute case system. Any MIME type is accepted, up to 50 MiB per file.

## Response `201`

File uploaded.

- DisputeEvidenceFile
  - `id` string, required
  - `type` 'dispute_evidence', required
  - `caseReference` string, required
  - `evidenceType` 'consolidated', required
  - `filename` string, required
  - `contentType` string, required
  - `size` integer, required
  - `createdAt` string, date-time, required

## Other responses

- `400` — Invalid multipart fields or multipart parsing failure. Parser-level failures, including files over 50 MiB, return text/plain.
- `401` — Missing, expired, or invalid access token.
- `403` — The token lacks the client_file_management scope.
- `500` — Unexpected server failure.

## Changes

> 4 revisions in range; 1 could not be searched.

- **2026-08-21** `6882c8d02fd7` — 2 info
  - the security scope `client_file_management` was added to the endpoint's security scheme `oauth`
  - the security scope `file_management` was removed from the endpoint's security scheme `oauth`
- **2026-07-26** `c49212f8f795` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/stitch/apis/stitch-api/changes/files/post.md)

---

[API](https://skmtc.dev/stitch/apis/stitch-api.md) · [All operations](https://skmtc.dev/stitch/apis/stitch-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/stitch/stitch-api/revisions/8c5a258567d0/schema)