<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mastodon API changes | Schedule Social Media</title><description>New entries in the Mastodon API changelog, each linked to the platform&apos;s own announcement.</description><link>https://schedulesocialmedia.com/</link><language>en</language><atom:link href="https://schedulesocialmedia.com/api-changes/rss/mastodon.xml" rel="self" type="application/rss+xml"/><item><title>Mastodon 5.0.0-beta.1 moves sign-up into the OAuth flow and deprecates POST /api/v1/accounts</title><link>https://schedulesocialmedia.com/api-changes/mastodon-5-0-beta-oauth-sign-up-accounts-deprecated-2026-11/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-5-0-beta-oauth-sign-up-accounts-deprecated-2026-11/</guid><description>Deprecation. Apps that create Mastodon accounts through POST /api/v1/accounts should move to the OAuth sign-up flow (prompt=create), and authentication errors now return HTTP 422 instead of HTTP 200. What to do: Send new users to /oauth/authorize with prompt=create (and invite_code when following an invite). Stop relying on POST /api/v1/accounts, handle HTTP 422 on auth errors, and use allow_nonfunctional on verify_credentials for unconfirmed or unapproved accounts.</description><pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate><category>Mastodon</category><category>Deprecation</category></item><item><title>Mastodon 4.7.1 and 4.7.5 fix password authentication bypasses (2FA with LDAP, PAM or SSO, and inactive accounts)</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-7-1-4-7-5-password-auth-bypass-fixes-2026-09/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-7-1-4-7-5-password-auth-bypass-fixes-2026-09/</guid><description>Security, effective 2026-09-01. On unpatched servers, two-factor sign-in for LDAP, PAM or SSO accounts and the check on inactive accounts could be bypassed, and disabled staff accounts kept admin API access. What to do: Admins should upgrade to 4.7.5 (or 4.6.7, 4.5.17, 4.4.24 or later for the September fixes on older branches). Tools need no API change.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate><category>Mastodon</category><category>Security</category></item><item><title>Mastodon 4.7 encrypts local keys and extends fediverse signature support</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-7-release-signatures-key-encryption/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-7-release-signatures-key-encryption/</guid><description>Version, effective 2026-08-20. Upgrading to 4.7 is a required stop for zero-downtime migrations to later versions, and local ActivityPub private keys are encrypted at rest. What to do: Admins should plan the upgrade through 4.7 before later versions. Zero-downtime upgrades from 4.6 are supported.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><category>Mastodon</category><category>Version</category></item><item><title>New terms of service for mastodon.social and mastodon.online, effective August 31, 2026</title><link>https://schedulesocialmedia.com/api-changes/mastodon-social-online-new-terms-of-service-2026-07/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-social-online-new-terms-of-service-2026-07/</guid><description>Policy, effective 2026-08-31. Everyone with an account on mastodon.social or mastodon.online, including accounts that post through scheduling tools, is bound by new user terms from August 31, 2026. A further update with service rules and DSA information is planned for December 2026. What to do: Read the new terms if you or your clients post from mastodon.social or mastodon.online, and watch for the December 2026 update that adds service rules.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>Mastodon</category><category>Policy</category></item><item><title>Mastodon 4.6.2 updates FFmpeg to fix critical CVE-2026-8461</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-6-2-ffmpeg-cve-2026-8461/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-6-2-ffmpeg-cve-2026-8461/</guid><description>Security, effective 2026-06-25. Container image deployments with an affected FFmpeg were exposed to a critical vulnerability until updated. What to do: Upgrade to Mastodon 4.6.2 or later, or update FFmpeg in your own image.</description><pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate><category>Mastodon</category><category>Security</category></item><item><title>Mastodon 4.6 adds profile endpoints that replace update_credentials</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-6-profile-endpoints-replace-update-credentials/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-6-profile-endpoints-replace-update-credentials/</guid><description>Version, effective 2026-06-17. Profile editing moves to new GET and PATCH /api/v1/profile endpoints, and the alt text limit rises to 10,000 characters. What to do: Use the new profile endpoints for profile edits. Admins should note FFmpeg 5.1 or later is now required and Node.js 20, Ruby 3.2 and ImageMagick support were removed.</description><pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate><category>Mastodon</category><category>Version</category></item><item><title>Mastodon 4.5 adds quote states to the API and enables RFC 9421 signatures</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-5-release-quote-api-rfc9421/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-5-release-quote-api-rfc9421/</guid><description>Version, effective 2025-11-06. Servers on 4.5 report quote states in the API and always use RFC 9421 HTTP signatures. What to do: Admins should note PostgreSQL 13 is no longer supported. Client developers can handle the new quote states.</description><pubDate>Thu, 06 Nov 2025 00:00:00 GMT</pubDate><category>Mastodon</category><category>Version</category></item><item><title>Mastodon 4.4 removes OAuth password grant and HTTP Basic auth, adds deprecation headers</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-4-removes-password-grant-basic-auth/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-4-removes-password-grant-basic-auth/</guid><description>Breaking, effective 2025-07-08. Apps that sign in with the OAuth password grant or HTTP Basic authentication stop working on servers running 4.4 or later. What to do: Switch to the standard OAuth authorization code flow. Servers run by different admins upgrade at different times, so expect a mixed fleet.</description><pubDate>Tue, 08 Jul 2025 00:00:00 GMT</pubDate><category>Mastodon</category><category>Breaking</category></item><item><title>Mastodon 4.3 adds PKCE, the profile scope and OAuth server metadata, and removes the crypto scope</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-3-pkce-profile-scope-oauth-metadata-2024-10/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-3-pkce-profile-scope-oauth-metadata-2024-10/</guid><description>Version, effective 2024-10-08. Apps that connect to Mastodon can use PKCE, ask for the narrower profile scope, register several redirect URIs and discover OAuth settings automatically. The crypto scope is gone. What to do: Use PKCE (S256) in the authorization code flow, request profile instead of read:accounts when you only need the user&apos;s identity, read /.well-known/oauth-authorization-server and api_versions to detect features, and drop the crypto scope from app registrations.</description><pubDate>Tue, 08 Oct 2024 00:00:00 GMT</pubDate><category>Mastodon</category><category>Version</category></item><item><title>Mastodon 4.2.10 and 4.1.18 fix API permission checks and posts scheduled under 5 minutes ahead</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-2-10-api-permission-checks-scheduled-posts-2024-07/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-2-10-api-permission-checks-scheduled-posts-2024-07/</guid><description>Security, effective 2024-07-04. Unpatched servers checked permissions incorrectly on several API endpoints and kept streaming sessions open after an app&apos;s token was revoked. Both releases also stop posts scheduled less than 5 minutes ahead from being published at once. What to do: Admins should run 4.2.10, 4.1.18 or later. Scheduling tools should send scheduled_at at least 5 minutes in the future, as the API documentation requires.</description><pubDate>Thu, 04 Jul 2024 00:00:00 GMT</pubDate><category>Mastodon</category><category>Security</category></item><item><title>Mastodon 4.2.5, 4.1.13 and 4.0.13 fix CVE-2024-23832, an origin validation flaw</title><link>https://schedulesocialmedia.com/api-changes/mastodon-4-2-5-cve-2024-23832-origin-validation-2024-02/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/mastodon-4-2-5-cve-2024-23832-origin-validation-2024-02/</guid><description>Security, effective 2024-02-01. Servers on older versions did not check strictly enough where incoming data came from. Mastodon fixed it in patched releases on February 1, 2024. What to do: Admins should run a patched version (4.2.5, 4.1.13 or 4.0.13 or later). Tool builders can check a server&apos;s version through /api/v2/instance before trusting it.</description><pubDate>Thu, 01 Feb 2024 00:00:00 GMT</pubDate><category>Mastodon</category><category>Security</category></item></channel></rss>