Mastodon API
POST /api/v1/accounts endpoint removal
Deprecated, no dateSubscribe to Mastodon APIShare
The POST /api/v1/accounts endpoint is deprecated without a shutdown date. It was deprecated in favor of the OAuth sign-up flow in version 5.0.0. Requests using this endpoint are slated to fail upon eventual removal.
Calls it hits
POST /api/v1/accounts
What to use instead of these calls
Send users through the OAuth sign-up flow via GET /oauth/authorize instead of registering accounts by API. Moving sign-up into the OAuth flow requires updating the application onboarding process rather than simply changing an endpoint call.
Moving sign-up into the OAuth flow changes the app's onboarding, not only a call.
In Mastodon API's words
5.0.0 - deprecated in favor of the OAuth sign-up flow
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 POST /api/v1/accounts 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/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.