![]()
matrix-client.matrix.org · CommunicationSubscribeShare
Matrix.org homeserver API breaking changes
The breaking changes Matrix.org homeserver API announced that Okapi tracks: 8 in all.
Do you run the Matrix.org homeserver API? Make sure your users call it right →
At a glance
- API host
matrix-client.matrix.org- Kind
- Communication
- Versions with breaking changes
- v3 (8)
- Breaking changes tracked
- 8 breaking changes with no date yet
- Last updated
Deprecated, no date yet 8
-
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 -
No date
POST /_matrix/client/v3/account/3pidEndpoint removal Deprecated, no date
Where Okapi reads it
- Changelog spec.matrix.org/latest/changelog/
- Announcement spec.matrix.org/latest/client-server-api/
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub