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
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
MED dispute identifier as returned by GET /v1/accounts/{accountId}/pix/med.
Headers
Optional client-generated idempotency token (recommended for safe retries).
Unix seconds. Required on the signed host; tolerance is 300s either way (403 request_timestamp_skew).
Lowercase hex SHA-256 of the body. An empty body hashes the empty string, so the header is always present. Mismatch returns 400 body_hash_mismatch.
Detached JWS (<protected>..<signature>, ES256 or PS256) over METHOD\nPATH?QUERY\nTIMESTAMP\nIDEMPOTENCY_KEY_OR_EMPTY\nX_CONTENT_SHA256.
Request
The key returned by evidence/upload-url.
Optional. Ties the attachment to a message of this dispute (clarification reply).