Transferwise
GET /v3/comparisons endpoint removal
Deprecated, no date
Transferwise has deprecated GET /v3/comparisons without announcing a shutdown date. Calls made to this endpoint will eventually fail as the provider notes it is deprecated. Check your integration to identify where this path is in use.
Calls it hits
GET /v3/comparisons
What to use instead of these calls
Request comparisons with GET /v4/comparisons instead.
In Transferwise's words
This endpoint is deprecated. Use the V4 comparison endpoint instead.
Facts
- API
- Transferwise
api.transferwise.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Transferwise's own pages
Questions
When does this change take effect?
Transferwise deprecated GET /v3/comparisons without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Transferwise has not given a shutdown date yet.
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 Transferwise 9
-
No date
GET /v1/accountsEndpoint removal Deprecated, no date -
No date
GET /v1/accounts/{}Endpoint removal Deprecated, no date -
No date
GET /v1/borderless-accountsEndpoint removal Deprecated, no date -
No date
GET /v1/cases/{}Endpoint removal Deprecated, no date -
No date
GET /v1/cases/{}/commentsEndpoint removal Deprecated, no date -
No date
POST /v1/borderless-accounts/{}/conversionsEndpoint removal Deprecated, no date -
No date
POST /v1/profilesEndpoint removal Deprecated, no date -
No date
PUT /v1/cases/{}/commentsEndpoint removal Deprecated, no date -
No date
PUT /v1/profilesEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.