Register an uploaded MED evidence file

Step 3 of 3, after the `PUT`. Without it the object stays in storage and never becomes part of the defense: this call is what links the bytes to the dispute. Every upload goes through real type checking, antivirus and sanitization before it counts as evidence — a few seconds. `scanStatus` reports that: `PENDING` while running, `APPROVED` when cleared, `REJECTED` with a `scanReason`. Rejected files do not travel with the defense.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

accountIdstringRequired
Account identifier.
idstringRequired

MED dispute identifier as returned by GET /v1/accounts/{accountId}/pix/med.

Headers

X-Tenant-IdstringRequired
Tenant context used for authorization and routing.
Idempotency-KeystringOptional

Optional client-generated idempotency token (recommended for safe retries).

Request

This endpoint expects an object.
keystringRequired

The key returned by evidence/upload-url.

evidenceIdstringOptional
filenamestringOptional
contentTypestringOptional
sizeByteslongOptional

Response

Evidence registered.
medIdstring
evidenceIdstring
registeredboolean
filenamestringOptional
scanStatusenumOptional
scanReasonstringOptional

Errors

400
Bad Request Error
404
Not Found Error
409
Conflict Error
422
Unprocessable Entity Error