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

# Evidence

`POST /v3/disputes/evidence/datapoints`

Submit structured textual datapoints for a dispute.

## Headers

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

## Request body

- DisputeEvidenceDatapointsRequestRequest — Submit structured textual datapoints for a dispute.
  - `airlineTicketNumbers` string[], nullable — Array of airline ticket numbers for the order
  - `customerCorrespondences` CustomerCorrespondence[], nullable — Array of objects describing correspondence between the merchant and the customer.
    - `contactDateTime` string, date, nullable — Date and time of the contact
    - `contactDescription` string, nullable — Description of the contact
    - `contactId` string, required — Contact ID
    - `contactReason` 'CANCELING' | 'EXCHANGE' | 'SICKNESS' | 'NAME_CHANGE' | 'INR' | 'OTHER', nullable — Reason for the contact
  - `itemsHeldInCustoms` string[], nullable — Array of item names that are being held in customs
  - `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).
  - `proofsOfCreditBalance` ProofOfCreditBalance[], nullable — Array of objects describing credit balance applications
    - `amount` number, nullable — Amount of the credit balance
    - `appliedDate` string, date, required — Date the credit balance was applied. Use YYYY-MM-DD format.
    - `currency` string, nullable — Currency of the credit balance, 3-letter ISO-4217 format currency code
  - `proofsOfDelivery` ProofOfDelivery[], nullable — Data proofs of delivery - array of objects with details of deliveries made.
    - `carrier` string, nullable — Shipping carrier name
    - `date` string, date, nullable — Delivery date. Use YYYY-MM-DD format.
    - `deliveryStatus` string, nullable — Current status of the delivery
    - `didCustomerSignForDelivery` boolean, nullable — Whether the customer signed for the delivery
    - `trackingNumber` string, nullable — Order tracking number
  - `proofsOfPickup` ProofOfPickup[], nullable — Array of objects describing pickup details
    - `pickupDate` string, date, nullable — Date of the pickup. Use YYYY-MM-DD format.
    - `providedIdentityVerificationMethods` string[], nullable — List of methods used to verify customer identity
    - `status` 'NOT_PICKED_UP' | 'PICKED_UP', required — Current status of the pickup
  - `proofsOfRefund` ProofOfRefund[], nullable — Data proofs of refund - Array of objects describing refunds issued.
    - `refundAmount` number, nullable — Refund amount in currency chosen by the buyer
    - `refundAuthorizationCode` string, nullable — Refund authorization code from payment gateway
    - `refundChargeId` string, nullable — The unique identifier associated with the refund charge. For example: ARN in Adyen, charge ID in Stripe, referenceNumber in Braintree, etc.
    - `refundCurrency` string, nullable — Transaction currency chosen by the buyer, 3-letter ISO-4217 format currency code
    - `refundDate` string, date, nullable — Date the refund was paid. Use YYYY-MM-DD format.
    - `refundTransactionId` string, required — Refund transaction id
    - `replacementItems` string[], nullable — List of items that were replaced as part of the refund
  - `proofsOfReplacement` ProofOfReplacement[], nullable — Array of objects describing order replacements
    - `replacementAmount` number, nullable — Amount of the replacement order
    - `replacementCurrency` string, nullable — Currency of the replacement order, 3-letter ISO-4217 format currency code
    - `replacementDate` string, date, nullable — Date the replacement was processed. Use YYYY-MM-DD format.
    - `replacementId` string, required — Unique identifier for the replacement order
    - `replacementItems` string[], nullable — List of items that were replaced
    - `replacementTrackingNumber` string, nullable — Tracking number for the replacement shipment
    - `shippingCarrier` string, nullable — Shipping carrier name for the replacement
  - `reservationIds` string[], nullable — Array of reservation IDs for the order
  - `subscriptionDetails` SubscriptionDetails[], nullable — Array of objects describing subscription details
    - `billingAgreementPolicy` string, nullable — The merchant's recurring billing agreement policy
    - `isRecurringCharge` boolean, required — Whether this is a recurring subscription charge

## Response `200`

Example disputeEvidenceDatapointsResponse

- DisputeEvidenceDatapointsResponse — The response object for dispute evidence datapoints uploads.
  - `invalidEvidenceDatapoints` InvalidEvidenceDataPoint[], nullable — Array of invalid datapoint entries, if any
    - `datapointPath` string, required — The path to the faulty datapoint in the evidence file ex: /customerCorrespondences/0/contactReason
    - `failureReason` string, required — The reason why the evidence was considered invalid
  - `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)