Get MED

Use this endpoint to get the details of a specific MED by its id.

Available Environments

Production

https://api.gateway.com.br/core

Endpoint

• Method: GET
• Endpoint: /med/{id}
• Authentication: Bearer token

Path Params

Name	Type	Required	Description	Validations
id	string (UUID v4)	Yes	MED identifier	Must be a valid UUID v4

Request Example

cURL

curl --request GET \
--url https://api.gateway.com.br/core/med/553e8400-e29b-41d4-a716-436251480000 \
--header 'Authorization: Bearer your-jwt-token'

JavaScript

const response = await fetch('https://api.gateway.com.br/core/med/553e8400-e29b-41d4-a716-436251480000', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer your-jwt-token'
  }
});

const data = await response.json();

Success Response

Field	Type	Required	Description
id	string	Yes	MED identifier
acquirer	string	Yes	Acquirer of the MED
transactionId	string	Yes	Transaction identifier
endToEnd	string	Yes	End-to-end identifier
notificationId	string	No	Identifier of the associated notification
status	string (enum) - PENDING, APPEALED, APPROVED, REJECTED	Yes	MED status
origin	string (enum) - ACQUIRER, ADMIN	Yes	Origin of the MED
reason	string (enum) - SCAM, FRAUDULENT_ACCESS, OPERATIONAL_ERROR, OTHER	Yes	Reason of the MED
amount	number	Yes	MED amount (integer, in cents)
paymentMethod	string (enum) - PIX	Yes	Payment method
payer	object	No	Payer data (see Sub-Object AccountHolder)
customerMessage	string	No	Customer message
user	object	Yes	User data (UserVo)
decisionMessage	string	No	Decision message
refundStatus	string (enum) - FULL_REFUND, PARTIAL_REFUND, INSUFFICIENT_FUNDS	No	Refund status
appealContent	object	No	Content of the defense (AppealContent)
refundAmount	number	No	Refund amount (integer, in cents)
statusHistory	array	Yes	Status history (see Sub-Object StatusHistory)
medDate	string (ISO)	Yes	Date of the MED
createdAt	string (ISO)	Yes	Creation date
updatedAt	string (ISO)	Yes	Last update date

Sub-Objects

UserVo

Field	Type	Required	Description
name	string	Yes	User name
email	string	Yes	User e-mail
createdAt	string (ISO)	Yes	Creation date of the user

AccountHolder

Field	Type	Required	Description
type	string (enum) - PF, PJ	Yes	Holder type
name	string	Yes	Holder name
document	string	Yes	Holder document
bankAccount	object	Yes	Bank data (see Sub-Object BankAccount)
pix	object	Yes	PIX key of the holder (see Sub-Object PixKeyVo)

BankAccount

Field	Type	Required	Description
type	string	Yes	Account type
digit	string	Yes	Account check digit
ispb	string	Yes	ISPB of the bank

PixKeyVo

Field	Type	Required	Description
key	string	Yes	PIX key
type	string (enum) - CPF, CNPJ, EMAIL, PHONE, EVP	Yes	PIX key type

StatusHistory (item)

Field	Type	Required	Description
status	string (enum) - PENDING, APPEALED, APPROVED, REJECTED	Yes	MED status in the history
date	string (ISO)	Yes	Date and time of the status change
durationInMilliseconds	number	No	Duration of the status in milliseconds

AppealContent

Field	Type	Required	Description
message	string	No	Defense message
evidences	array	No	Evidence of the defense (see Sub-Object FileVo)

FileVo (item of evidences)

Field	Type	Required	Description
key	string	Yes	File key
isPrivate	boolean	Yes	Whether the file is private
expirationDate	string (ISO)	No	File expiration date
url	string	No	Signed URL of the file

Response Example

{
  "id": "553e8400-e29b-41d4-a716-436251480000",
  "acquirer": "ACQUIRER_EXEMPLO",
  "transactionId": "553e8400-e29b-41d4-a716-446655440000",
  "endToEnd": "E2E12345678",
  "notificationId": null,
  "status": "APPEALED",
  "origin": "ACQUIRER",
  "reason": "FRAUDULENT_ACCESS",
  "amount": 1000,
  "paymentMethod": "PIX",
  "payer": {
    "type": "PF",
    "name": "Fulano de Tal",
    "document": "***456789**",
    "bankAccount": {
      "type": "CHECKING",
      "digit": "7",
      "ispb": "12345678"
    },
    "pix": {
      "key": "12345678910",
      "type": "CPF"
    }
  },
  "customerMessage": "Cliente informou não reconhecer a cobrança.",
  "user": {
    "name": "Loja Exemplo",
    "email": "contato@lojaexemplo.com",
    "createdAt": "2026-03-01T09:00:00.000Z"
  },
  "decisionMessage": "Defesa recebida e em análise.",
  "refundStatus": "FULL_REFUND",
  "appealContent": {
    "message": "Anexamos comprovante de entrega.",
    "evidences": [
      {
        "key": "med/evidence-1.pdf",
        "isPrivate": true,
        "expirationDate": "2026-03-25T10:00:00.000Z",
        "url": null
      }
    ]
  },
  "refundAmount": 1000,
  "statusHistory": [
    {
      "status": "PENDING",
      "date": "2026-03-24T10:00:00.000Z",
      "durationInMilliseconds": 3600000
    },
    {
      "status": "APPEALED",
      "date": "2026-03-24T11:00:00.000Z",
      "durationInMilliseconds": 1800000
    },
    {
      "status": "APPROVED",
      "date": "2026-03-24T11:30:00.000Z",
      "durationInMilliseconds": null
    }
  ],
  "medDate": "2026-03-24T10:00:00.000Z",
  "createdAt": "2026-03-24T10:00:00.000Z",
  "updatedAt": "2026-03-24T11:30:00.000Z"
}

Possible Errors

Code	Description	Solution
401	Invalid credentials	Check your credentials
403	No permission/authorization	Contact support
404	MED not found	Check the id you sent
500	Internal error	Contact support