Hi Martin, Transitions should be completely seamless with no observable impact to bots, tools, or other integrations that are currently running. It will just be business as usual!
To emphasize this change is purely adding another pass through layer to our routing infrastructure. Previous rerouting efforts related to the RESTBase sunsetting project included shifting what underlying services the API calls were going to, which resulted in some unintentional differences between service behaviors. In this case, there are no changes to endpoint behavior, calling structure, nor application services. I've actually been referring to this change as the "invisible gateway" for that reason -- literally nothing is changing besides going through a new pass through, so you shouldn't even notice the shift. Thanks, Halley *Halley Coplin* (she/her) Sr. Product Manager, MediaWiki Interfaces Wikimedia Foundation <https://wikimediafoundation.org/> On Mon, Oct 6, 2025 at 11:01 AM Martin Domdey <[email protected]> wrote: > What happens with running bots and tools during rerouting time? > > Doc Taxon > > Halley Coplin <[email protected]> schrieb am Mo., 6. Okt. 2025, 18:54: > >> Howdy API artists, tool tinkerers, and bot builders, >> >> We are starting to reroute all web API traffic through a common API >> Gateway. We will begin transitioning traffic for endpoints under the >> rest.php path the week of Monday, October 6. This change will be performed >> through a phased rollout, starting with Group 0 and Group 1 wikis, then >> proceeding across all remaining wiki groups and projects. We expect all >> traffic to be rerouted on or before Oct 17. >> >> This is purely introducing another layer of infrastructure, and we expect >> the change to be non-breaking and non-disruptive. We are also keeping a >> close eye out for any anomalies as we dial up proportional traffic. If any >> issues are observed, please file a phabricator ticket to the Service Ops >> team board <https://phabricator.wikimedia.org/tag/serviceops/>. >> >> Why is this change happening? >> >> As mentioned in the API as a Product Tech Blog >> <https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-the-current-and-next-generation-of-technical-contributors/> >> published earlier this year and as part of the WE5 objective >> <https://meta.wikimedia.org/wiki/Talk:Wikimedia_Foundation_Annual_Plan/2025-2026#Responsible_Use_of_Infrastructure_(WE5)> >> (KR5.2), we are working to consolidate and centralize our API >> infrastructure. Centralizing API routing will make observability across >> APIs easier, allowing us to make better data-driven decisions. Having a >> single, centralized API gateway also simplifies API management, enabling us >> to continue streamlining and standardizing our API offerings. >> >> What’s next? >> >> In Q2, we will tackle rerouting the Action API through the same API >> Gateway, with additional APIs in future quarters. Keep an eye out for more >> updates here and on Tech News <https://meta.wikimedia.org/wiki/Tech/News> >> ! >> >> >> >> Feel free to respond here or reach out directly if you have any >> questions, comments, or concerns! >> >> Thanks, >> >> Halley >> >> *Halley Coplin* (she/her) >> Sr. Product Manager, MediaWiki Interfaces >> Wikimedia Foundation <https://wikimediafoundation.org/> >> _______________________________________________ >> Wikitech-l mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> >> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/ > > _______________________________________________ > Wikitech-l mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
_______________________________________________ Wikitech-l mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
