Matrix.org homeserver API
POST /_matrix/client/v3/account/3pid endpoint removal
Deprecated, no dateSubscribe to Matrix.org homeserver APIShare
The POST /_matrix/client/v3/account/3pid endpoint has been deprecated without a shutdown date. Calls to this endpoint will eventually fail as it is phased out. The change affects any client interacting with third-party identifier management on the homeserver.
Calls it hits
POST /_matrix/client/v3/account/3pid
What to use instead of these calls
Call POST /_matrix/client/v3/account/3pid/add or /account/3pid/bind instead.
In Matrix.org homeserver API's words
This endpoint is deprecated in favour of the more specific /3pid/add and /3pid/bind endpoints.
Facts
- API
- Matrix.org homeserver API
matrix-client.matrix.org - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Matrix.org homeserver API's own pages
Questions
When does this change take effect?
Matrix.org homeserver API deprecated POST /_matrix/client/v3/account/3pid without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Matrix.org homeserver 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 Matrix.org homeserver API 7
-
No date
GET /_matrix/client/v3/eventsEndpoint removal Deprecated, no date -
No date
GET /_matrix/client/v3/events/{id}Endpoint removal Deprecated, no date -
No date
GET /_matrix/client/v3/initialSyncEndpoint removal Deprecated, no date -
No date
GET /_matrix/media/v3/configEndpoint removal Deprecated, no date -
No date
GET /_matrix/media/v3/download/*Endpoint removal Deprecated, no date -
No date
GET /_matrix/media/v3/preview_urlEndpoint removal Deprecated, no date -
No date
GET /_matrix/media/v3/thumbnail/{id}/{id}Endpoint 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.