Get a MED dispute
Everything from the list plus the timeline visible to the account holder (events), the messages exchanged with the review (messages), the attachments with signed downloadUrl (evidences), the steps CorpX already executed in the return (steps) and the can* flags saying what is enabled right now. In info_requested, infoRequest carries the review’s question and its deadline.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
The medId.
Headers
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.
Response
Infraction report id. Same value as data.medId in the webhooks.
Disputed amount. Amount in BRL. Max 2 decimal places (e.g., 150.75 for R$150,75).
Stage of CorpX's review. awaiting_defense → pending_review (→ info_requested → pending_review) → in_execution → refunded | awaiting_funds, or refused.
Timeline visible to the account holder; message texts are in Portuguese.
Return steps CorpX already executed, in text. Appears from in_execution on.
Free-text details from the claimant, when present.
openedAt + 48h. Nothing is auto-rejected on expiry: the dispute stays alive, the client just loses the chance to state their case.
Deadline of the pending clarification, in info_requested.
Amount currently held, in BRL. 0 when nothing is held.
Disputed amount minus refundedTotal.
true when the dispute closed with a partial return.
The review's question, present in info_requested.