Upload an evidence file to a dispute
Streams an evidence file (pdf, png, jpeg, or csv) to tenant-scoped object storage and records the resulting object key on the dispute as a new evidence item. The comment arrives as a query parameter and the file bytes as the request body. The tenant is resolved from the JWT and the dispute from the path — never from the body. Fails closed (503) when object storage is not configured; rejects oversize bodies (413) and unsupported content types (415).
Authorizations
Bearer token authentication (format: "Bearer {token}")
Headers
Evidence media type: application/pdf, image/png, image/jpeg, or text/csv
"application/pdf"
Path Parameters
Dispute ID (UUID)
"550e8400-e29b-41d4-a716-446655440001"
Query Parameters
Comment describing the uploaded evidence
1 - 1000"Bank statement showing correct amount"
Body
The body is of type file.
Response
Created
Dispute details
Category of the dispute
BANK_FEE_ERROR, UNRECOGNIZED_CHARGE, DUPLICATE_TRANSACTION, OTHER "BANK_FEE_ERROR"
Creation timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"
Description of the dispute
"Transaction amount differs from expected"
Evidence submitted for this dispute
Exception ID this dispute is for
"019c96a0-10d2-7134-ba5f-664142ee7052"
Unique identifier for the dispute
"019c96a0-10d2-7193-8841-0d7347efd09a"
User who opened the dispute
"user@example.com"
Reason for reopening if reopened
"New evidence discovered"
Resolution description when closed
"Counterparty confirmed error"
Current state
DRAFT, OPEN, PENDING_EVIDENCE, WON, LOST "OPEN"
Last update timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"

