Matrix.org homeserver API
GET /_matrix/media/v3/config endpoint removal
Deprecated, no dateSubscribe to Matrix.org homeserver APIShare
Matrix.org homeserver API deprecated the GET /_matrix/media/v3/config endpoint without a shutdown date. It will be removed in a future release, after which requests to this route will fail. This change impacts all callers relying on the legacy media config path.
Calls it hits
GET /_matrix/media/v3/config
What to use instead of these calls
Call GET /_matrix/client/v1/media/config with an access token instead.
In Matrix.org homeserver API's words
This API is deprecated and will be removed from a future release. Replaced by GET /_matrix/client/v1/media/config
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 GET /_matrix/media/v3/config 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/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 -
No date
POST /_matrix/client/v3/account/3pidEndpoint 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.