/api/partner/v1/disputes/{disputeId}Report the outcome
Report what happened to the dispute.
submitted once you sent the evidence (stops the deadline reminder), then won or lost; accepted if you conceded.
Authorization
X-Api-Key headerSend your partner key on every request. An owner key acts for its one owner; an integration token also needs the owner's id in the X-Owner-Id header.
Path parameters
disputeIdstringpathrequiredOur dispute id, or your Stripe dispute id (du_…).
Body
application/jsonstatusstringrequiredsubmitted | won | lost | accepted, or any Stripe dispute status.
Response
200 · application/jsonsuccessbooleanrequireddataobjectidstringstripeDisputeIdstringchargeIdstringreasonstringnetworkReasonCodestringnullableamountnumbercurrencystringstatusstringStripe vocabulary.
evidenceDueBystring <date-time>nullableevidenceStatusstringcollectingreadyfailednot_applicablerecommendationstringnullablecontestacceptnullrecommendationReasonstringnullablegenuine_duplicatebank_instrument_reasonnullevidenceobjectStripe evidence fields by Stripe's own names (product_description, customer_name, service_date, access_activity_log, uncategorized_text, duplicate_charge_explanation, …). Text fields are strings; file fields (receipt, service_documentation, customer_signature, customer_communication, uncategorized_file, duplicate_charge_documentation) are { "fileId": "…" }.
filesDisputeFile[]warningsstring[]submittedAtUtcstring <date-time>nullablecreatedAtUtcstring <date-time>updatedAtUtcstring <date-time>errorstringnullable