Mastodon API
POST /api/v1/media version retirement
Deprecated, no dateSubscribe to Mastodon APIShare
Mastodon API deprecated POST /api/v1/media without a shutdown date. Subsequent calls will eventually fail once the endpoint is retired. This change affects any integration using POST /api/v1/media for uploads.
Calls it hits
POST /api/v1/media
What to use instead of these calls
Upload using POST /api/v2/media instead, and poll GET /api/v1/media/{id} until the url is set.
In Mastodon API's words
3.1.3 - deprecated in favor of POST /api/v2/media , which is equal to v1 in all aspects, except it returns HTTP 202
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 POST /api/v1/media 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
/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.