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
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/>