Okapi Okapi

Transferwise POST /v1/profiles endpoint removal

Deprecated, no date

Transferwise has deprecated the POST /v1/profiles endpoint without a shutdown date. Calls made to this route will eventually fail. The provider notes that the endpoint is deprecated and directs callers to newer profile creation endpoints.


Calls it hits

  • POST /v1/profiles

What to use instead of these calls

Create profiles with POST /v2/profiles/personal-profile or POST /v2/profiles/business-profile.

In Transferwise's words

This endpoint is deprecated. Please see the Create Personal Profile and Create Business Profile v2 endpoints.

Transferwise, Announcement

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 POST /v1/profiles 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

  1. No date GET /v1/accountsEndpoint removal Deprecated, no date
  2. No date GET /v1/accounts/{}Endpoint removal Deprecated, no date
  3. No date GET /v1/borderless-accountsEndpoint removal Deprecated, no date
  4. No date GET /v1/cases/{}Endpoint removal Deprecated, no date
  5. No date GET /v1/cases/{}/commentsEndpoint removal Deprecated, no date
  6. No date GET /v3/comparisonsEndpoint removal Deprecated, no date
  7. No date POST /v1/borderless-accounts/{}/conversionsEndpoint removal Deprecated, no date
  8. No date PUT /v1/cases/{}/commentsEndpoint removal Deprecated, no date
  9. 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.

Add to GitHub