Attach dispute evidence
Attaches dispute evidence to a dispute via the engine (`POST /v1/disputes/:id/evidence`). Hyperswitch's evidence submission is JSON-based (the pre-pivot Finix multipart file-upload flow no longer has a backend), so the parsed JSON evidence body is forwarded verbatim. Pass an `Idempotency-Key` header to make the attach safe to retry. This attaches evidence but does NOT finalize it — call `POST /api/disputes/{id}/submit` to commit the response to the connector.
Note: requires the `disputes:write` scope, which is defined in the scope catalog but is NOT included in the default API-key grant — keys must be explicitly granted `disputes:write`.
Authentication
x-api-keystring
A scoped MvsPayApiKey, e.g. mvspay_live_…. Mint and scope keys from the dashboard (Settings → API Keys).
Path parameters
id
The dispute id.
Headers
Idempotency-Key
Client-supplied idempotency key to make the attach safe to retry.
Request
This endpoint expects an object.
evidence_type
The kind of evidence being attached (e.g. shipping_documentation, receipt, customer_communication).
uncategorized_text
Free-text supporting statement.
Response
Evidence attached.
success
Errors
400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
500
Internal Server Error
502
Bad Gateway Error