Mastodon API
/api/v1/filters* version retirement
Deprecated, no dateSubscribe to Mastodon APIShare
Mastodon API deprecated the /api/v1/filters* endpoints without announcing a shutdown date. Calls made to these endpoints will eventually fail. The change affects any requests relying on the v1 filter implementation.
Calls it hits
/api/v1/filters*
What to use instead of these calls
Manage filters with the v2 filters API (/api/v2/filters).
In Mastodon API's words
View your filters deprecated GET /api/v1/filters HTTP / 1.1 Returns: List of V1::Filter OAuth: User token + read:filters Version history: 2.4.3 - added 4.0.0 - deprecated.
Facts
- API
- Mastodon API
mastodon.social - Kind
- Version retirement
- 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 /api/v1/filters* 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
GET /api/v1/trendsEndpoint removal Deprecated, no date -
No date
POST /api/v1/accountsEndpoint removal Deprecated, no date -
No date
POST /api/v1/mediaVersion 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.