For #Mastodon app developers and fellow #fediverse platform developers, with the approaching Mastodon 4.6 release we've put together an overview of new and changed APIs that you may want to look at!

[mastodonengineering@mastodon.social]

For #Mastodon app developers and fellow #fediverse platform developers, with the approaching Mastodon 4.6 release we've put together an overview of new and changed APIs that you may want to look at! Collections, profile editing, #Wrapstodon, and more:

Mastodon 4.6 for Developers

Mastodon 4.6 contains several technical changes that developers will want to learn about.

Mastodon Blog (blog.joinmastodon.org)

[andre_601@swiss.social]

@MastodonEngineering I have to say, the version thing in your API is the most confusing one I've ever seen.

You bumped the API version to 10, yet you're still using v2 (And in some other cases like collections apparently still v1) in the URL for the API, which kinda defeats the point of the version to begin with.
That's awful REST API design in all honesty and doesn't help people to understand what API is new and what isn't.

If the v1 is a typo, please correct it.

[gargron@mastodon.social]

@andre_601 @MastodonEngineering The URL path of the API versions endpoints. This allows us to avoid breaking compatibility as we can add a newer method while keeping the older one intact. This is only necessary when breaking changes are involved. The API version number which is 10, is a number that goes up whenever a new feature is available in the API, allowing client developers to know in advance which features will be available.

[woodcat@mastodon.social]

@MastodonEngineering

Oops…