GET /collections/notifications/{} → endpoint removal
Mercado Libre API
Stopped working
On October 2, 2024, Mercado Libre API discontinued the Collections API endpoint GET /collections/notifications/{}. Calls made to this endpoint to validate payment status fail after that date.
Calls it hits
GET /collections/notifications/{}
What to use instead of these calls
Read the payment with GET api.mercadopago.com/v1/payments/{id} using the Payments API, taking the payment ID from the IPN notification resource field.
In Mercado Libre 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 Libre API
api.mercadolibre.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 Libre API's own pages
Questions
When does this change take effect?
Calls to GET /collections/notifications/{} on Mercado Libre 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.
More from Mercado Libre API 1
-
No date
GET /orders/{}/billing_infoEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.