Circle API
POST /v1/payments/{id}/refund endpoint removal
Stopped workingSubscribe to Circle APIShare
On April 3, 2025, the POST /v1/payments/{id}/refund endpoint was removed. Calls made to this endpoint fail. The endpoint was previously deprecated and removed from the Crypto Deposits API.
Calls it hits
POST /v1/payments/{id}/refund
What to use instead of these calls
Refund a crypto deposit with POST /v1/paymentIntents/{id}/refund.
In Circle API's words
The following endpoints were deprecated and removed from the Crypto Deposits API:
Facts
- API
- Circle API
api.circle.com - Kind
- Endpoint removal
- Announced
- April 3, 2025
- Takes effect
- April 3, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Circle API's own pages
Questions
When does this change take effect?
Calls to POST /v1/payments/{id}/refund on Circle API stopped working on April 3, 2025.
What happens to calls after April 3, 2025?
They have failed since April 3, 2025.
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 Circle API 5
-
POST /v1/paymentsEndpoint removal Stopped working -
POST /v1/payments/{id}/cancelEndpoint removal Stopped working -
POST /v1/payments/{id}/captureEndpoint removal Stopped working -
/v1/cards*Removal Stopped working -
No date
/v1/notifications/subscriptions*Endpoint 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.