GET /collections/notifications/{} → endpoint removal
Mercado Pago API
Stopped working
On October 2, 2024, Mercado Pago removed the GET /collections/notifications/{} endpoint used by integrations to check payment status. Requests sent to this endpoint after this date fail.
Calls it hits
GET /collections/notifications/{}
What to use instead of these calls
To validate payment status, read the payment using GET /v1/payments/{id} in the Payments API, obtaining the payment ID from the resource field of the IPN notification.
In Mercado Pago API's words
We are working on discontinuing the Collections API [/collections/notifications/] which is used by some integrations to validate the status of their payments. The official discontinuation date will be 02/10/2024
Facts
- API
- Mercado Pago API
api.mercadopago.com - Kind
- Endpoint removal
- Announced
- May 29, 2024
- Takes effect
- October 2, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Mercado Pago API's own pages
Questions
When does this change take effect?
Calls to GET /collections/notifications/{} on Mercado Pago API stopped working on October 2, 2024.
What happens to calls after October 2, 2024?
They have failed since October 2, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.