Mastodon API
GET /api/v1/trends endpoint removal
Deprecated, no dateSubscribe to Mastodon APIShare
The Mastodon API deprecated the GET /api/v1/trends endpoint without a shutdown date. Mastodon API notes that it is a deprecated alias that may be removed in the future. Once removed, requests to this endpoint fail.
Calls it hits
GET /api/v1/trends
What to use instead of these calls
Call GET /api/v1/trends/tags instead.
In Mastodon API's words
method signature changed from GET /api/v1/trends to GET /api/v1/trends/tags . The former is a deprecated alias that may be removed in the future.
Facts
- API
- Mastodon API
mastodon.social - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Mastodon API's own pages
Questions
When does this change take effect?
Mastodon API deprecated GET /api/v1/trends without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Mastodon 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 Mastodon API 5
-
No date
GET /api/v1/instanceVersion retirement Deprecated, no date -
No date
GET /api/v1/suggestionsVersion retirement Deprecated, no date -
No date
POST /api/v1/accountsEndpoint removal Deprecated, no date -
No date
POST /api/v1/mediaVersion retirement Deprecated, no date -
No date
/api/v1/filters*Version retirement 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.