Submit Dispute Counter

Submit a draft counter's evidence to the payment processor. This is **one-shot and terminal for this round**: the evidence is sent to the processor as your final response, the counter moves to `submitted`, and it can no longer be edited. Only a `draft` counter on a dispute that is currently awaiting a response (e.g. Stripe `needs_response`) can be submitted — otherwise the call returns `400`. Every attached file must both belong to you and have passed a malware scan (`clean`); otherwise the submission is rejected with `422` and nothing is sent. The dispute itself transitions (e.g. to `under_review`) when the processor's webhook confirms receipt, not synchronously here.

Authentication

x-truemed-api-keystring

Sales channel API key for merchant server-to-server authentication

Path parameters

business_idstringRequired

The Truemed dispute ID (UUID).

counter_idstringRequired

The Truemed counter ID (UUID).

Response

Successful response
counter_idstring

Stable Truemed counter ID (UUID).

created_atdatetime
When this counter was created.
phaseenum
Dispute phase this counter responds to.
revisioninteger

Optimistic-lock revision; echo it back on the next draft save to detect conflicts.

stateenum
Counter lifecycle state.
updated_atdatetime
When this counter was last updated.
evidence_itemslist of objectsDefaults to []
The categorized evidence captured on this counter.
submitted_atdatetime or null
When this counter was submitted to the processor.
submitted_bystring or null

Email of the dashboard user who submitted this counter; null for drafts or API-key submissions.

Errors

400
Bad Request Error
404
Not Found Error
405
Method Not Allowed Error
500
Internal Server Error
501
Not Implemented Error