Howdy friends,
The Wikimedia Math API
<https://www.mediawiki.org/w/index.php?api=wmf-math%2Fv1&title=Special%3ARes…>
is now deprecated. We plan to fully remove support by the end of September
2026. Developers who are calling these endpoints are advised to transition
to alternative math rendering solutions, such as relying on native browser
support for MathML <https://www.w3.org/TR/mathml4/> or other client-side
solutions.
== Why are we deprecating and removing these endpoints? ==
Mathoid is now the only service remaining on RESTBase, blocking its path to
sunsetting (which began in 2019
<https://www.mediawiki.org/wiki/RESTBase/deprecation>). By removing these
endpoints, we may fully disable the RESTBase service, which supports our
goal of consolidation and reducing infrastructure costs.
We are able to move forward with this sunsetting because maturity and
support for MathML has improved across browsers, reducing the need for the
custom math rendering solution. Starting in July 2026, Wikimedia projects
began transitioning to utilize native browser rendering instead of relying
on Mathoid. Native browser rendering is now available as a user preference.
Wikimedia projects now also offer client-side MathJax
<https://www.mathjax.org/> support <https://www.mathjax.org/> to improve
rendering where the maturity and support for MathML rendering is not fully
covered, to ensure that we maintain a high quality math experience within
Wikimedia projects. In either scenario, the server-side rendering approach
offered through Mathoid via RESTBase is no longer required.
== When will these endpoints be fully sunset and disabled? ==
Once all Wikimedia projects have switched from Mathoid to native MathML +
MathJax, we will move quickly on sunsetting the Math endpoints and
completing the RESTBase sunsetting effort. We currently expect the
Wikimedia switch to be complete by the end of August 2026, and plan to
fully disable the Mathoid endpoints by the end of September 2026. Prior to
the final sunsetting date, we will have some ‘brown out’ windows where the
API service will be temporarily disabled to ensure all users are aware of
the change and can address unexpected breakages. We will also monitor
traffic coming from community owned tools and work with tool owners where
needed to transition to alternative solutions where needed.
== What does this mean for third-party MediaWiki users? ==
Some third party MediaWiki users rely on the Mathoid endpoints outside of
WMF owned features. MediaWiki 1.43 (the previous LTS) already removed
reliance on Mathoid in favor of native MathML. Third-parties who rely on
the Math extension and mathematical formulas are encouraged to upgrade to
MW 1.43+ to avoid disruption to formula rendering. The upcoming MW 1.47 LTS
(targeting November release
<https://www.mediawiki.org/wiki/Version_lifecycle>) will also include the
same client-side MathJax support seen in Wikimedia projects to provide the
best experience for all MediaWiki installations.
== What does this mean for rendering custom math formulas outside of
MediaWiki? ==
Requests for adhoc formula rendering outside of a MediaWiki context will no
longer be supported. Alternative approaches are required, such as migrating
to use native MathML or implementing a client-side alternative.
== Will this result in a major version change for the MediaWiki REST API? ==
No. Due to adoption outside of Wikimedia hosted projects, we decided to
proceed with removal without a major API version increment to minimize
disruption for other developers in the community. The Math endpoints are
part of the Wikimedia REST API, which is predominantly used by Wikimedia
Foundation owned features and mobile applications.
== Where can I get more information about the deprecation process? ==
For more information about our approach to deprecation overall, see the new API
Deprecation <https://www.mediawiki.org/wiki/API/Deprecation> page for more
information about deprecation processes.
If you have any questions, comments, or suggestions, please don’t be shy
about reaching out here, or tagging us on a talk page.
Thanks,
Halley, Mateus, and Timo
*Halley Coplin* (she/her)
Sr. Product Manager, MediaWiki Interfaces
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello and happy Friday!
An API Strategy Brief is now published on mediawiki.org:
https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Artifacts/API_Str…
This strategy brief covers the direction we're taking Wikimedia's API
ecosystem over the next few years, including touching on topics like: why APIs
are so important for powering the future of Wikimedia projects, how the
current landscape has grown fragmented and hard to navigate, what we're
doing to make it more consistent and better documented, and where community
developers fit in.
The strategy is written for and applies to anyone building on top of
Wikimedia APIs
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Artifacts/API_Per…>,
not just internal teams. This strategy was also predominantly informed by
conversations with Wikimedian developers through Listening Tours, Hackathon
engagements, and more, so I'd like to continue that trend and make sure our
strategy reflects what the community actually needs.
If you have thoughts, questions, or concerns, please feel free to post to
the talk page, or message me directly via email, Discord, Telegram, smoke
signals, or however else you'd like to get in touch.
Thanks!
Halley
[PS]: I am also starting to work on a companion doc that goes deeper into
our AI + API strategy, specifically. If that's a space that interests you,
or if you increasingly feel like you identify as a 'vibe coder', I'd love
to talk! :) Feel free to grab time on my calendar
<https://calendar.app.google/B6SBKQVgK7CQ8VXy9>, send your thoughts through
email, or comment on the talk page for the API Strategy Brief.
*Halley Coplin* (she/her)
Sr. Product Manager, MediaWiki Interfaces
Wikimedia Foundation <https://wikimediafoundation.org/>