---
title: "Evidence file upload"
method: POST
path: "/v3/disputes/evidence/file"
tags: ["Disputes"]
---

# Evidence file upload

`POST /v3/disputes/evidence/file`

Upload a single file as dispute evidence.

## Headers

- `api-version` string, required
- `x-forter-siteid` string, required
- `Authorization` string, required

## Request body

- DisputeEvidenceFileRequestRequest — Upload a single file as dispute evidence.
  - `evidenceType` 'ACCEPTANCE_OF_RECURRING_BILLING_AGREEMENT' | 'AUTHENTICATION_CERTIFICATE' | 'BUYER_REVIEW_SURVEY' | 'CARDHOLDER_VERIFICATION_DOCUMENT' | 'CHARGEBACK_NOTIFICATION' | 'CONTRACT_PAGE' | 'CREDIT_BALANCE' | 'CUSTOMER_CORRESPONDENCE' | 'DELAY_DISCLOSURE' | 'DISPUTE_LETTER' | 'EMAIL_CONFIRMATION' | 'FLIGHT_MANIFEST' | 'HOTEL_NO_SHOW' | 'INVOICE' | 'OTHER' | 'PASSENGER_OR_CUSTOMER_DETAILS' | 'PROOF_OF_DELIVERY' | 'PROOF_OF_ORDER_REPLACEMENT' | 'PROOF_OF_POSSESSION_OR_USAGE' | 'PROOF_OF_RECURRING_AGREEMENT_NOTICE' | 'PROOF_OF_REFUND' | 'PROOF_OF_REQUESTED_CANCELLATION' | 'PROOF_OF_RESIDENCE' | 'PURCHASE_HELD_IN_CUSTOMS' | 'RECEIPT' | 'RECURRING_BILLING_AGREEMENT' | 'RELATED_INVOICE_HISTORY' | 'SIGNED_DELIVERY_FORM' | 'SIGNED_ORDER_FORM' | 'SOCIAL_NETWORK_REPUTATION' | 'STATEMENT_OF_UNAUTHORIZED_DEBIT' | 'TERMS_AND_CONDITIONS' | 'USER_TERMS_AND_CONDITION_ACCEPTANCE', required — The type of evidence being uploaded. The following types are supported: - ACCEPTANCE_OF_RECURRING_BILLING_AGREEMENT - AUTHENTICATION_CERTIFICATE - BUYER_REVIEW_SURVEY - CARDHOLDER_VERIFICATION_DOCUMENT - CHARGEBACK_NOTIFICATION - CONTRACT_PAGE - CREDIT_BALANCE - CUSTOMER_CORRESPONDENCE - DELAY_DISCLOSURE - DISPUTE_LETTER - EMAIL_CONFIRMATION - FLIGHT_MANIFEST - HOTEL_NO_SHOW - INVOICE - OTHER - PASSENGER_OR_CUSTOMER_DETAILS - PROOF_OF_DELIVERY - PROOF_OF_ORDER_REPLACEMENT - PROOF_OF_POSSESSION_OR_USAGE - PROOF_OF_RECURRING_AGREEMENT_NOTICE - PROOF_OF_REFUND - PROOF_OF_REQUESTED_CANCELLATION - PROOF_OF_RESIDENCE - PURCHASE_HELD_IN_CUSTOMS - RECEIPT - RECURRING_BILLING_AGREEMENT - RELATED_INVOICE_HISTORY - SIGNED_DELIVERY_FORM - SIGNED_ORDER_FORM - SOCIAL_NETWORK_REPUTATION - STATEMENT_OF_UNAUTHORIZED_DEBIT - TERMS_AND_CONDITIONS - USER_TERMS_AND_CONDITION_ACCEPTANCE
  - `filePath` string, required — An S3 pointer for the file
  - `orderId` string, nullable — Unique order/transaction identifier. Should match the order id sent to Forter at checkout. Note that Forter treats this ID as case-insensitive; Order123 and ORDER123 will be identified as the same order.
  - `processorCaseNumber` string, nullable — The case number from the payment processor.
  - `processorChargeId` string, nullable — The unique identifier of the payment, such as Acquirer Reference Number (ARN).

## Response `200`

Example disputeEvidenceFileResponse

- DisputeEvidenceFileResponse — The response object following uploading dispute evidence file request to the system
  - `message` 'EVIDENCE_UPLOADED' | 'SERVICE_UNAVAILABLE' | 'SCHEMA_VALIDATION_FAILED' | 'CLAIM_NOT_FOUND', required — The message containing status response text
  - `status` 'SUCCESS' | 'FAILED', required — Status of the request processing

## Other responses

- `400` — Bad Request (Often missing a required parameter)
- `401` — Unauthorized (No valid API key provided)
- `404` — Not Found (The requested item doesn't exist)
- `429` — Too Many Requests (The client exceeded a rate limit). Honor Retry-After before retrying.
- `500` — Server Error (Something went wrong on Forter's end)
- `default` — Typed error envelope for any undeclared 4xx / 5xx status.

---

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