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/>
_______________________________________________
Mediawiki-api-announce mailing list -- mediawiki-api-announce(a)lists.wikimedia.org
To unsubscribe send an email to mediawiki-api-announce-leave(a)lists.wikimedia.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/>
_______________________________________________
Mediawiki-api-announce mailing list -- mediawiki-api-announce(a)lists.wikimedia.org
To unsubscribe send an email to mediawiki-api-announce-leave(a)lists.wikimedia.org
Hello,
In MediaWiki 1.42, within the list=tag API query module, the tag source
type named "extension" was renamed to "software" [1]. The "extension"
entries were made to still appear alongside "software" in the tag source
list but were deprecated [2][3]. A patch to remove this compatibility
behavior was merged, meaning that the "extension" entries will no longer
appear. This change is expected to roll out in 1.47.0-wmf.12. See
https://www.mediawiki.org/wiki/MediaWiki_1.47/Roadmap for a schedule of
deployment to Wikimedia wikis.
[1] https://phabricator.wikimedia.org/T247552
[2]
https://en.wikipedia.org/w/api.php?action=query&list=tags
&tgprop=source&tglimit=max
[3]
https://lists.wikimedia.org/hyperkitty/list/mediawiki-api
-announce(a)lists.wikimedia.org/thread/EL3ECIAJWSBBMGDH2SXH6EJOQJWRGKAJ/
_______________________________________________
Mediawiki-api-announce mailing list -- mediawiki-api-announce(a)lists.wikimedia.org
To unsubscribe send an email to mediawiki-api-announce-leave(a)lists.wikimedia.org
Hello,
In MediaWiki 1.42, within the list=tag API query module, the tag source
type named "extension" was renamed to "software" [1]. The "extension"
entries were made to still
appear alongside "software" in the tag source list but were deprecated
[2][3]. There are plans to remove this compatibility behavior in the
next major version of MediaWiki (1.47), so that the "extension" entries
will no longer appear.
The use of "extension" is misleading because it does not exclusively
refer to tags defined by MediaWiki extensions (via the onListDefinedTags
hook), but also those defined in MediaWiki core (via
ChangeTagsStore::DEFINED_SOFTWARE_TAGS). The distinction isn't really
useful to clients anyway.
[1] https://phabricator.wikimedia.org/T247552
[2]
https://en.wikipedia.org/w/api.php?action=query&list=tags&tgprop=source&tgl…
[3]
https://lists.wikimedia.org/hyperkitty/list/mediawiki-api-announce@lists.wi…
_______________________________________________
Mediawiki-api-announce mailing list -- mediawiki-api-announce(a)lists.wikimedia.org
To unsubscribe send an email to mediawiki-api-announce-leave(a)lists.wikimedia.org
Hi all,
Summary: The API Portal wiki[1] is shutting down. API keys created on the
API Portal will continue to work (rate limits apply). api.wikimedia.org
endpoints will be deprecated gradually starting in July 2026. Documentation
on the API Portal is moving to mediawiki.org[2].
== Context ==
Started in 2020, the API Portal is an experimental wiki available at
api.wikimedia.org. It was designed by the Wikimedia Foundation as a home
for Wikimedia API docs and related functionality. The Wikimedia Foundation
has decided to shut down the API Portal as part of a new strategy for
Wikimedia APIs[3] and to focus on new ways to make API docs easy to find,
use, and create.
== Changes ==
Endpoints:
api.wikimedia.org endpoints will continue to work as currently documented
until at least June 2026. Starting in the second half of 2026, these
endpoints will be migrated to new routes, and the old routes will be
deprecated gradually. Deprecation information will be communicated through
the mediawiki-api-announce mailing list[4], Wikimedia API changelog[5], and
on the project talk page[6].
Rate limits:
Starting in late March or early April 2026, api.wikimedia.org endpoints
will have the same rate limits[7] as other Wikimedia APIs. The new rate
limits are higher than the current rate limits[8], so this change should
not create any issues. The Lift Wing API will continue to have the same
custom rate limits[9] with only minor clarifications.
API keys:
We expect API keys created through the API Portal to continue to work
normally within the API rate limits[7]. You can manage your API keys
through Meta-Wiki[10]. If you encounter any issues, please reach out using
the contact information below.
Documentation:
Documentation from the API Portal is currently being consolidated and moved
to other technical documentation wikis. Starting in June 2026, the API
Portal will be inaccessible. To learn about Wikimedia APIs and find links
to docs, visit the new landing page (work in progress) on mediawiki.org[2].
== Contact ==
If you have any questions, want to share your feedback, or have any issues
with functionality related to the API Portal:
- Post to the project talk page[6]
- Email techdocs(a)wikimedia.org
== Learn more ==
For a timeline, background behind the decision, and the latest project
information, see the project page[11].
Best,
- Alex Paskulin on behalf of the Wikimedia Tech Docs Team and MediaWiki
Interfaces Team
[1]: https://api.wikimedia.org/wiki/Main_Page
[2]: https://www.mediawiki.org/wiki/Wikimedia_APIs
[3]:
https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-th…
[4]:
https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wi…
[5]: https://www.mediawiki.org/wiki/Wikimedia_APIs/Changelog
[6]: https://wikitech.wikimedia.org/wiki/Talk:API_Portal/Deprecation
[7]: https://www.mediawiki.org/wiki/Wikimedia_APIs/Rate_limits
[8]:
https://wikitech.wikimedia.org/wiki/API_Portal/Deprecation#API_Portal_histo…
[9]: https://api.wikimedia.org/wiki/Lift_Wing_API/Rate_limits
[10]: https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/list
[11]: https://wikitech.wikimedia.org/wiki/API_Portal/Deprecation
--
Alexandra Paskulin
Technical Writer
Wikimedia Foundation
_______________________________________________
Mediawiki-api-announce mailing list -- mediawiki-api-announce(a)lists.wikimedia.org
To unsubscribe send an email to mediawiki-api-announce-leave(a)lists.wikimedia.org
Hi
Forwarding this message from wikitech-l as it's also relevant to this list.
The the new API rate limits
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Rate_limits> were deployed
as planned yesterday.
If you encounter any issues with these rate limits, please let us know.
Edge cases that are known to be potentially problematic include bots that
use owner-only tokens to authenticate but do not support cookies, gadgets
that make heavy use of the API, and external browser-based apps or games
that make a lot of API calls.
We have done our best to mitigate these and provide options, but please do
contact us at bot-traffic(a)wikimedia.org if you are unsure as to the best
path forward.
Best
Jonathan
---------- Forwarded message ---------
From: Jonathan Tweed <jtweed(a)wikimedia.org>
Date: Fri, 24 Apr 2026 at 10:36
Subject: Roll out of global API rate limits for identified requests
To: Wikitech-l <wikitech-l(a)lists.wikimedia.org>
Hi
We are now ready to start rolling out the next phase of global API rate
limits. As previously announced
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>,
this will apply to all API requests, including those that we class as
identified.
The full set of limits
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Rate_limits> have now been
published on wiki, along with answers to frequently asked questions
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Rate_limits/FAQ> that we
received after the roll out of limits to anonymous requests. We will
gradually ramp down to the published limits, starting from next Tuesday
28th April. We expect to be at the final limits by the end of May.
As part of this change we have moved from per-hour limits to per-minute
limits, so please bear that in mind when you first look at the docs! This
is preferable, as it helps smooth aggregate request rates and also minimises
the impact on any user that inadvertently hits a limit.
These limits are based on extensive analysis of API request data, but it is
possible that some bots or gadgets may still trigger rate limits. We will
be actively monitoring all relevant spaces, so please do let us know if you
need help to work out the best way forward should this happen.
Thank you for your engagement with this. I hope from our actions it is
clear that we are not trying to limit community usage, but protect our
projects from automated usage at a scale we cannot support
<https://diff.wikimedia.org/2026/03/26/quo-vadis-crawlers-progress-and-whats…>
without ensuring it is a fair and sustainable use
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Responsible_Reuse>
of resources.
Best
Jonathan
--
Jonathan Tweed (he/him)
Senior Product Manager, Core Platform
Wikimedia Foundation
_______________________________________________
Mediawiki-api-announce mailing list -- mediawiki-api-announce(a)lists.wikimedia.org
To unsubscribe send an email to mediawiki-api-announce-leave(a)lists.wikimedia.org
Good news, everyone!
A new Attribution API <https://www.mediawiki.org/wiki/Attribution_API>
module is now available as a beta
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Stability_policy> on all
Wikimedia Foundation hosted wiki projects. The purpose of this API is to
make it easier to appropriately attribute Wikimedia project content when
it’s presented or referenced in off-wiki contexts. This API directly
supports the Wikimedia Attribution Framework
<https://wikimedia-attribution.toolforge.org/>, which provides specific
guidelines for how to appropriately attribute content across different
reuse scenarios and form factors.
What does it do?
The Attribution API <https://www.mediawiki.org/wiki/Attribution_API>makes
it easy to follow the guidelines outlined in the Wikimedia Attribution
Framework <https://wikimedia-attribution.toolforge.org/>. The API provides
the information required by each attribution signal in a single,
well-structured and easy-to-use endpoint. Although the recommended
attribution information was largely already available through existing
APIs, this approach significantly simplifies the process for developers,
which we believe will make it more likely that developers will follow the
recommended standards.
Who is it for?
Appropriate attribution is critical for all reuse scenarios where Wikimedia
content will be presented off-wiki, as it ensures that the content is
fairly credited and that external readers remain aware of the Wikimedia
projects and communities it came from. This means that if you make games,
offer search services, use project content for research, build alternative
reader experiences, or contribute to anything else happening off-wiki, you
probably need to properly attribute Wikimedia content!
This specific API is also primarily intended for mission-supporting users
and use cases. Wikimedia Enterprise will offer similar information in their
structured responses for scaled commercial reuse.
How do I participate?
We encourage everyone to try out the endpoints and give us your feedback on
the project discussion page
<https://www.mediawiki.org/w/index.php?title=Talk:Attribution_AP>!
Additionally, if you discover what you think might be a bug, please feel
free to file an issue directly to the MediaWiki Interfaces Phabricator board
<https://phabricator.wikimedia.org/project/view/6931/>.
Major changes will minimally be announced on the project page
<https://www.mediawiki.org/wiki/Attribution_API>. If you are interested in
this capability, we recommend that you add the page to your watchlist to
stay informed with the latest changes and calls for targeted feedback. Some
of these changes may also be announced here or through Tech News, but the
nature of a beta does not guarantee broad communication of every change.
What should I expect?
This API is available on all Wikimedia projects, and is initially being
released as a beta
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Stability_policy>. Reference
documentation can be found in the REST API sandbox
<https://www.mediawiki.org/w/index.php?title=Special:RestSandbox&api=attribu…>
on any Wikimedia wiki (such as the REST API sandbox on English Wikipedia
<https://en.wikipedia.org/w/index.php?api=attribution.v0-beta&title=Special%…>).
Although available everywhere, the Attribution API only explicitly supports
Wikipedia articles and media files hosted through either Wikipedia or
Commons. We need your help testing and shaping additional project and
content types to help inform how the information should be structured.
We are continuing to iterate and refine the API. Although we expect the
interface itself to remain relatively stable, the specific returned values
are subject to change over time. Breaking changes to adjust the interface
or response structures may also occur during the beta period as we respond
to emerging feedback and feature requests.
Following the beta period, we will elevate the API to a stable v1. This
will be done after we are satisfied with meeting user expectations and when all
high priority issues are resolved. Although there is not yet a firm date
for when we will elevate this experience, we expect it to happen around
September 2026, depending on the nature of requests that arise during the
beta period. Additional communications will happen closer to the stable
version launch date to ensure the community is aware of the upcoming change.
Please feel free to reach out directly here or post on the project
discussion page
<https://www.mediawiki.org/w/index.php?title=Talk:Attribution_AP> if you
have any questions, comments or concerns! We look forward to your feedback
and support in helping us refine this API, as well as the beta process
itself.
Thanks, and happy attribution!
Halley
*Halley Coplin* (she/her)
Sr. Product Manager, MediaWiki Interfaces
Wikimedia Foundation <https://wikimediafoundation.org/>
_______________________________________________
Mediawiki-api-announce mailing list -- mediawiki-api-announce(a)lists.wikimedia.org
To unsubscribe send an email to mediawiki-api-announce-leave(a)lists.wikimedia.org
Hi all
As previously announced
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>,
we have started rolling out new global API rate limits across our APIs to
help ensure fair and sustainable access
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Content_Reuse>
to Wikimedia resources.
We have just enabled the first set of limits, which apply to anonymous
requests from bots and unauthenticated requests from web browsers. See the
documentation on mediawiki.org
<https://www.mediawiki.org/wiki/Wikimedia_APIs/Rate_limits> for more
information. This has now been updated with actual limits for anonymous
requests and authenticated bot requests that do not come from WMCS. We are
still finalizing the initial limits for User-Agent only (e.g.
InstantCommons) and authenticated browser requests.
As a next step, rate limits for logged in users will follow in early April
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Responsible_Reuse…>.
The concrete limits will be communicated beforehand. Access for clients
running in WMCS and accounts that have a bot flag will not be affected by
this change. However, all developers are advised to familiarize themselves
with the new limits and follow the best practices outlined in the
documentation.
If you see any unexpected issues that might be the result of the limits
rolled out this week, we are actively monitoring relevant mailing lists,
Talk pages and bot-traffic(a)wikimedia.org.
Best
Jonathan
--
*Jonathan Tweed* (he/him)
Senior Product Manager, Core Platform
Wikimedia Foundation <https://wikimediafoundation.org/>
_______________________________________________
Mediawiki-api-announce mailing list -- mediawiki-api-announce(a)lists.wikimedia.org
To unsubscribe send an email to mediawiki-api-announce-leave(a)lists.wikimedia.org
Creating a motivating study space can help students stay focused and productive. Custom LED neon signs with phrases like “Stay Focused” or “Keep Going” can act as daily reminders of academic goals. Modern LED neon signs are energy-efficient, customizable in colours, fonts, and sizes, and are designed to create a vibrant and inspiring environment.
If you’re interested in designing one for your study area, you can explore custom options here:
https://oasisneonsigns.co.uk/