Wise Platform API
PUT /v1/profiles endpoint removal
Deprecated, no dateSubscribe to Wise Platform APIShare
Wise Platform API deprecated the PUT /v1/profiles endpoint without a shutdown date. Calls to this endpoint will fail. The change affects any client using the legacy profile update route.
Calls it hits
PUT /v1/profiles
What to use instead of these calls
Update profiles using PUT /v2/profiles/{profileId}/personal-profile or PUT /v2/profiles/{profileId}/business-profile instead.
In Wise Platform API's words
This endpoint is deprecated. Please see the Update Personal Profile and Update Business Profile v2 endpoints.
Facts
- API
- Wise Platform API
api.wise.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Wise Platform API's own pages
Questions
When does this change take effect?
Wise Platform API deprecated PUT /v1/profiles without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Wise Platform API 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 Wise Platform API 9
-
No date
GET /v1/accountsEndpoint removal Deprecated, no date -
No date
GET /v1/accounts/{id}Endpoint removal Deprecated, no date -
No date
GET /v1/borderless-accountsEndpoint removal Deprecated, no date -
No date
GET /v1/cases/{id}Endpoint removal Deprecated, no date -
No date
GET /v1/cases/{id}/commentsEndpoint removal Deprecated, no date -
No date
GET /v3/comparisonsEndpoint removal Deprecated, no date -
No date
POST /v1/borderless-accounts/{id}/conversionsEndpoint removal Deprecated, no date -
No date
POST /v1/profilesEndpoint removal Deprecated, no date -
No date
PUT /v1/cases/{id}/commentsEndpoint 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.